Skip to main content
Glama

scope_delete

Destructive

Delete a scope and its caller default bindings while preserving its statistics. Use it to clean up obsolete scope definitions without losing recorded stats.

Instructions

Delete a scope (its caller default bindings go with it; stats remain).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "scope_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description's genuine contribution is the side-effect detail: caller default bindings are removed while stats are preserved, which is information not available in the structured fields. It does not address irreversibility, whether dependent bindings block deletion, or required permissions, so it adds useful but partial context.

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

Conciseness5/5

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

One sentence, front-loaded with the action, with the destructive side effect packed into a compact parenthetical. Nothing is wasted and the most consequential fact follows immediately after the verb.

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?

An output schema exists, so return values need not be explained, and annotations cover the destructiveness. Combined with the disclosure of what is deleted alongside the scope and what survives, the definition is nearly complete; only the identity of the 'name' parameter and any failure preconditions remain unaddressed.

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 0% for the single required parameter 'name', so the schema does not clarify whether it is a scope name or identifier. The description's phrasing 'a scope' only weakly implies that name identifies the target scope, adding marginal meaning beyond the bare schema.

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 a specific verb and resource ('Delete a scope'), which is unambiguous and separates it from siblings like scope_create, scope_update, and policy_delete by resource. It lacks any explicit reference to alternatives, but the resource+verb pairing is clear enough for an agent to select it.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as scope_update or scope_unbind_caller. The parenthetical side-effect note implies caution but does not tell the agent under what conditions deletion is the right action.

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