Skip to main content
Glama

scope_unbind_caller

Drops a caller’s default scope binding, ensuring the caller no longer inherits that scope by default.

Instructions

Drop a caller's default scope binding.

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": {
      "caller_key": "<caller_key>"
    },
    "name": "scope_unbind_caller"
  }
}

Input Schema

NameRequiredDescriptionDefault
caller_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only declare that this is a non-read-only, non-open-world, non-idempotent, non-destructive call, which the description does not build on at all. It does not say what happens if the caller has no binding (error vs. no-op), whether the caller falls back to another scope, or what permissions are needed — all material for a mutation whose idempotentHint is false.

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?

A single front-loaded sentence with no wasted words. Brevity is a virtue here, though the sentence is arguably too thin rather than padded.

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

Completeness2/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, but for a mutation tool with one undocumented parameter and no annotation detail, the description omits error behavior, state effects, and prerequisites. It is not complete enough for an agent to call confidently without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter, and the description only hints that caller_key identifies 'a caller'. It adds no format, source, or uniqueness information beyond the property name, so it does not compensate for the coverage gap.

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 names a specific verb ('Drop') and a specific resource ('a caller's default scope binding'), which cleanly inverts the sibling scope_bind_caller. It stops short of explicitly contrasting with siblings or stating what 'default' means, so it is clear but not fully differentiating.

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 guidance, no stated prerequisites (e.g., must a binding exist first?), and no mention of alternatives such as scope_bind_caller or list_bindings for verification. Usage is only implied by the verb.

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