Skip to main content
Glama

context_read

Read-onlyIdempotent

Access the context read operations listed below. Compatibility dispatcher; prefer the individually named tool when available. Select operation and its matching payload. Supported operations: get_context_graph, get_context_overview. Effects and required fields depend on that operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYesArguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation.
operationYesExact operation to dispatch; prefer its individually named tool when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "operation": {
      -        "const": "get_context_graph",
      -        "type": "string"
      -      },
      -      "payload": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "executionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "projectId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "sessionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "projectId"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "operation",
      -      "payload"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "operation": {
      -        "const": "get_context_overview",
      -        "type": "string"
      -      },
      -      "payload": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "executionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "projectId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "sessionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "projectId"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "operation",
      -      "payload"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "operation": {
      +        "const": "get_context_graph",
      +        "description": "Select this exact operation; payload must match this branch.",
      +        "type": "string"
      +      },
      +      "payload": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "executionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "projectId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "sessionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "projectId"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "operation",
      +      "payload"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "operation": {
      +        "const": "get_context_overview",
      +        "description": "Select this exact operation; payload must match this branch.",
      +        "type": "string"
      +      },
      +      "payload": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "executionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "projectId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "sessionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "projectId"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "operation",
      +      "payload"
      +    ],
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / operation / description
      Added value: +"Exact operation to dispatch; prefer its individually named tool when available."
    • addedInput schema / properties / payload / description
      Added value: +"Arguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the dispatcher nature and the hedge that 'Effects and required fields depend on that operation,' without describing what the operations actually do or produce. Minimal added behavioral context beyond structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the dispatcher role and the preference to use named tools, followed by the operation list. Four short sentences, none obviously redundant, though 'Effects and required fields depend on that operation' is filler that restates the polymorphic schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a compatibility shim whose parameters and safety are fully covered by schema and annotations, the description is adequate. It stops short of explaining the difference between get_context_graph and get_context_overview, which an agent must choose between when the named tools are unavailable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents 'operation' and 'payload' with enum consts per branch. The description's 'Select operation and its matching payload' reinforces the oneOf dispatch contract but adds no syntax or format detail beyond what the schema provides — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a 'Compatibility dispatcher' for context read operations and enumerates the two supported operations (get_context_graph, get_context_overview), so the agent knows exactly what it routes to. The verb 'Access' is generic, but the dispatcher framing plus the operation list makes the purpose concrete enough to distinguish this from write/other read tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: 'prefer the individually named tool when available,' which tells the agent this is a fallback path. It does not, however, explain when each of the two operations (graph vs overview) is appropriate, so the choice inside the dispatcher is left to the named siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources