Skip to main content
Glama

scope_write

Idempotent

Access the scope write operations listed below. Compatibility dispatcher; prefer the individually named tool when available. Select operation and its matching payload. Supported operations: curate_scope_panels. 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": "curate_scope_panels",
      -        "type": "string"
      -      },
      -      "payload": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "details": {
      -            "additionalProperties": false,
      -            "properties": {
      -              "referenceIds": {
      -                "items": {
      -                  "maxLength": 500,
      -                  "minLength": 1,
      -                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -                  "type": "string"
      -                },
      -                "maxItems": 100,
      -                "type": "array",
      -                "uniqueItems": true
      -              },
      -              "status": {
      -                "maxLength": 200,
      -                "minLength": 1,
      -                "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -                "type": "string"
      -              },
      -              "summary": {
      -                "maxLength": 240,
      -                "type": "string"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "executionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "idempotencyKey": {
      -            "maxLength": 128,
      -            "minLength": 16,
      -            "pattern": "^[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",
      -          "idempotencyKey"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "operation",
      -      "payload"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "operation": {
      +        "const": "curate_scope_panels",
      +        "description": "Select this exact operation; payload must match this branch.",
      +        "type": "string"
      +      },
      +      "payload": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "details": {
      +            "additionalProperties": false,
      +            "description": "Optional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content.",
      +            "properties": {
      +              "referenceIds": {
      +                "items": {
      +                  "maxLength": 500,
      +                  "minLength": 1,
      +                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +                  "type": "string"
      +                },
      +                "maxItems": 100,
      +                "type": "array",
      +                "uniqueItems": true
      +              },
      +              "status": {
      +                "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"
      +              },
      +              "summary": {
      +                "maxLength": 240,
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "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"
      +          },
      +          "idempotencyKey": {
      +            "description": "Caller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action.",
      +            "maxLength": 128,
      +            "minLength": 16,
      +            "pattern": "^[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",
      +          "idempotencyKey"
      +        ],
      +        "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

B3.1/5.0
Behavior2/5

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

Annotations already declare it is a mutation (readOnlyHint=false), idempotent, and non-destructive, so the safety profile is covered. The description adds only 'Effects and required fields depend on that operation,' which defers rather than discloses behavior. It offers no detail on what state is modified, auth requirements, or side effects beyond what the annotations provide.

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?

The description is brief and front-loads the dispatcher nature and the prefer-the-named-tool guidance. The final sentence ('Effects and required fields depend on that operation') is somewhat filler but does not bloat the text.

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 single-operation compatibility shim with full schema coverage and annotations covering safety and idempotency, the description is minimally adequate. It does not, however, explain what curate_scope_panels accomplishes, leaving the agent to infer behavior from the operation name alone.

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 coverage is 100%, so the baseline is 3 and the schema already documents operation, payload, projectId, and idempotencyKey in depth. The description only says 'Select operation and its matching payload,' which restates the schema structure without adding any new parameter meaning.

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

Purpose3/5

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

It states it is a compatibility dispatcher for 'scope write operations' and names the single supported operation, curate_scope_panels. However, 'scope write operations' is vague about what is actually being written or curated, and it never explains what the operation does. It distinguishes itself from the sibling curate_scope_panels only by telling the agent to prefer that tool.

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?

The description explicitly routes the agent: 'prefer the individually named tool when available,' naming the alternative tool that exists in the sibling list. It gives clear context on when this dispatcher is appropriate (compatibility fallback) but no explicit when-not conditions beyond that.

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