Skip to main content
Glama

scope_read

Read-onlyIdempotent

Access the scope read operations listed below. Compatibility dispatcher; prefer the individually named tool when available. Select operation and its matching payload. Supported operations: get_ownership, get_pending_scope_organizations. 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_ownership",
      -        "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_pending_scope_organizations",
      -        "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_ownership",
      +        "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_pending_scope_organizations",
      +        "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 that 'effects and required fields depend on that operation,' which is a deferral rather than disclosed behavior. With annotations carrying the load, a 3 is appropriate.

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 prefer-the-named-tool directive, followed by the operation list. Every sentence carries signal, with only mild redundancy in 'access the scope read operations listed below.'

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

Completeness4/5

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

For a two-operation dispatcher with full schema coverage and complete safety annotations, the description explains the dispatch pattern and routes to the named alternatives. It does not describe what the underlying operations return, but no output schema exists and the wrapped tools are themselves siblings, so this is a minor gap.

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%: the operation enum and payload fields are documented in the schema itself. The description's 'select operation and its matching payload' restates the dispatch contract but adds no format or semantic detail beyond it. Baseline 3 applies.

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?

States a specific role (compatibility dispatcher for scope read operations) and names the two supported operations, get_ownership and get_pending_scope_organizations. It is distinguishable from the sibling tools it wraps, though 'scope read operations' alone is vague until the operation list is read.

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?

Explicitly tells the agent to prefer the individually named tool when available, which is direct routing guidance to the alternatives. It doesn't spell out the condition under which the dispatcher itself is the right choice (e.g. legacy clients), but the core when-to-use signal is present.

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