Skip to main content
Glama

confirm_binding

Idempotent

Confirms a binding in the review queue, moving its provenance from automatic to manual so users can validate resolved data mappings.

Instructions

Confirm a binding in the review queue (provenance -> manual).

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": {
      "binding_id": "<binding_id>"
    },
    "name": "confirm_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
binding_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, non-destructive, idempotent), so the description doesn't need to restate safety. The "provenance -> manual" note usefully discloses the resulting state change, but it doesn't say what confirmation does to the record beyond that, whether it can be reversed, or what permissions are required.

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?

One short, front-loaded sentence with no filler. The parenthetical arrow notation is compact but slightly cryptic, which keeps it from being maximally clear.

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 needn't be explained, and the annotations cover idempotency and safety. Still, for a state-mutating tool the description leaves out preconditions and the effect on provenance/confidence data, so it is only adequate rather than complete.

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?

There is a single parameter, binding_id, with 0% schema description coverage, and the description adds no meaning about it (no format, source, or how to obtain a valid id, e.g. from list_bindings). With low coverage the description should compensate, and it does not.

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?

Specific verb+resource ("Confirm a binding") with a scope qualifier ("in the review queue") and a state transition hint ("provenance -> manual"). An agent can distinguish this from update_binding or list_bindings without opening the schema, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

"In the review queue" implies this applies to pending/unconfirmed bindings, which is usable context. However, there is no explicit when-not guidance, no statement of prerequisites (does the binding need to be in a particular state?), and no mention of update_binding as the alternative for non-confirmation edits.

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