Skip to main content
Glama

scope_list_bindings

Read-onlyIdempotent

List caller default-scope bindings to see which scope each caller resolves to, optionally filtered to a single caller.

Instructions

List caller default-scope bindings (optionally one caller's).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
caller_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the meaningful scope constraint that results are limited to default-scope bindings, but says nothing about ordering, result limits, or what happens for an unknown caller.

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?

A single front-loaded sentence with the resource first and the optional filter in parentheses; there is no wasted wording and the core message is immediate.

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?

An output schema exists, so return values need not be explained, and the tool is a simple one-parameter read. However, the description never clarifies the domain concept of a "default-scope binding" or the caller_key format, leaving gaps for a jargon-heavy resource.

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 for the single caller_key parameter is 0%, so the description carries the burden of explaining it. "Optionally one caller's" implies that supplying caller_key narrows results to that caller while omitting it lists all, which is useful, but the expected format/identifier semantics of caller_key are never described.

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 gives a specific verb ("List") and a precise resource ("caller default-scope bindings"), so an agent knows exactly what the tool returns. It does not distinguish itself from the sibling list_bindings or scope_list, so a 4 rather than a 5.

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?

The phrase "optionally one caller's" hints at a filtering mode but never states when to use this tool rather than list_bindings, scope_list, or scope_stats. No exclusions, prerequisites, or alternative-selection guidance are present.

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