Tool: lookup_context
Retrieves rich metadata regarding one or more data assets along with their relationships.
The following sample demonstrate how to use curl
to invoke the lookup_context
MCP tool.
| Curl Request |
|---|
curl --location 'https://dataplex.googleapis.com/mcp' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/call", "params": { "name": "lookup_context", "arguments": { // provide these details according to the tool' s MCP specification } } , "jsonrpc" : "2.0" , "id" : 1 } ' |
Input Schema
Lookup Context using permissions in the source system.
LookupContextRequest
| JSON representation |
|---|
{ "name" : string , "resources" : [ string ] } |
| Fields | |
|---|---|
name
|
Required. The project to which the request should be attributed in the following form: projects/{project}/locations/{location}. |
resources[]
|
Required. A list of up to 10 resource names from the same location. Name of a resource is in the following format: projects/{project_id_or_number}/locations/{location}/entryGroups/{group}/entries/{entry}. Example for a BigQuery table: 'projects/{project_id_or_number}/locations/{location}/entryGroups/@bigquery/entries/bigquery.googleapis.com/projects/{project_id}/datasets/{dataset_id}/tables/{table_id}'. This is the same value which is returned by the search_entries tool's response in the dataplexEntry.name field. |
Output Schema
Lookup Context response.
LookupContextResponse
| JSON representation |
|---|
{ "context" : string } |
| Fields | |
|---|---|
context
|
LLM Context for the requested resources. |
Tool Annotations
Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ✅
