Skip to main content
Glama

list_bindings

Read-onlyIdempotent

Lists column-to-concept bindings, optionally filtered by concept code, to help agents inspect how data concepts map to physical columns.

Instructions

List column->concept bindings (optionally filtered by concept code).

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

Input Schema

NameRequiredDescriptionDefault
concept_codeNo

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and an output schema covers the return shape, so the description only needs to add context. It contributes the fact that filtering is optional (unfiltered = full listing), but says nothing about pagination, result size, or whether bindings span one scope or all scopes.

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?

One short sentence, front-loaded with the resource and followed by the only qualifier that matters (the optional filter). Nothing redundant or padded.

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 simple one-parameter read tool with full annotations and an output schema, most requirements are met. The significant remaining gap is disambiguation from scope_list_bindings, which the description never addresses despite the confusingly similar name.

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 is 0% and the single parameter is undocumented in the schema, but the description does explain its meaning: an optional concept-code filter. It does not describe the expected code format or matching behavior (exact vs prefix), so it partially, not fully, compensates 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 (List) and a specific resource (column->concept bindings), so an agent knows exactly what comes back. It does not, however, differentiate this from the near-identically named sibling scope_list_bindings, leaving the agent to guess which listing surface is intended.

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 only usage cue is that filtering by concept code is optional, which implies an unfiltered call returns everything. There is no statement of when to prefer this over scope_list_bindings, propose_bindings, or review_bindings, and no prerequisites or exclusions.

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