Skip to main content
Glama

propose_bindings

Idempotent

Proposes column-to-concept bindings for review and confirmation, withholding low-confidence candidates until they meet the threshold.

Instructions

Propose column->concept bindings (propose-and-confirm; below-threshold withheld).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations establish the safety profile (not read-only, idempotent, non-destructive), and the description adds genuinely new behavior beyond them: proposals are staged rather than committed, and low-confidence candidates are withheld from the output. That filter behavior is important for interpreting results and is not derivable from the schema or annotations.

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 compact sentence with no filler, but the telegraphic parenthetical style ("propose-and-confirm; below-threshold withheld") makes the reader work harder than necessary, and the threshold criterion is never named.

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 there are no parameters to document. Still, a zero-argument tool that produces bindings leaves a real gap: it never says what corpus or scope it draws from or what a 'below-threshold' cutoff means, which the agent needs to interpret an empty result.

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?

Zero parameters, which is the baseline-4 case; there are no inputs whose meaning needs explaining. The description correctly spends no words on parameters and instead focuses on behavior.

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?

Names a specific verb and resource ("Propose column->concept bindings"), which is clearly distinct from siblings like confirm_binding, review_bindings, and list_bindings. It lacks any indication of what the proposal operates over, but the core action is unambiguous.

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?

The parenthetical "propose-and-confirm" implies this is the first step of a two-stage workflow that confirm_binding presumably completes, which is useful routing context. However, it never states when to call this versus review_bindings or confirm_binding, nor any preconditions, so the agent must infer the workflow.

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