Skip to main content
Glama

review_bindings

Read-onlyIdempotent

Fetches the below-threshold review queue for propose-and-confirm binding decisions, enabling agents to inspect candidate bindings that require manual approval.

Instructions

Return the below-threshold review queue (propose-and-confirm).

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": "review_bindings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are a filtered 'below-threshold' subset tied to a review workflow, but does not explain the threshold, ordering, or what happens when the queue is empty; the output schema presumably covers the return shape.

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 filler. The parenthetical is terse to the point of opacity rather than wasteful, which is a minor rather than structural flaw.

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 parameterless read-only tool with an output schema, the description covers the essentials, but the central qualifier 'below-threshold' is never defined, leaving the agent unable to reason about why certain bindings appear here versus in list_bindings. One clarifying clause would close the gap.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. Baseline of 4 applies.

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?

The description states a verb and a resource ('Return the below-threshold review queue') and the parenthetical ties it to a propose-and-confirm workflow. However, 'below-threshold' is undefined, so an agent cannot tell what qualifies an item for this queue, and the relation to siblings like list_bindings and confirm_binding is only hinted at.

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 parenthetical '(propose-and-confirm)' vaguely implies this is the review step in that flow, but there is no explicit when-to-use, when-not-to-use, or named alternative among list_bindings, propose_bindings, or confirm_binding. An agent must infer the workflow position.

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