Skip to main content
Glama

update_binding

Idempotent

Update a concept binding's confidence score, provenance, or review status to keep semantic mappings accurate and governed.

Instructions

Update concept binding confidence/provenance/review status.

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": {
      "column_id": "<column_id>",
      "concept_code": "<concept_code>",
      "entity_type": "<entity_type>"
    },
    "name": "update_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewedNoOptional reviewed flag update
column_idYesFunctionColumn.id to update
confidenceNoOptional confidence score update
provenanceNoOptional provenance update (llm/manual/admin)
entity_typeYesTarget entity type
concept_codeYesTarget concept code

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description only needed to add context. It adds almost none: notably it never explains the null-default semantics of the optional fields (whether passing null leaves the value untouched or clears it) or what happens if the binding does not exist. The sentence largely restates the tool name plus the field list already visible in the schema.

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 and the resource stated before the mutable fields. It is efficient, though the terseness is close to under-specification rather than crisp summarization.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with six parameters, the description leaves out partial-update semantics, identity/targeting rules for the three required keys, and any failure or no-op behavior. Annotations and the output schema cover safety and return shape, but the core update semantics an agent must get right are absent.

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 description coverage is 100%, so the schema already documents all six parameters, including the llm/manual/admin provenance hint and the default nulls. The description adds nothing about how column_id, concept_code and entity_type jointly identify the target binding, so baseline 3 applies.

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 ("Update") and resource ("concept binding") and enumerates the fields being changed (confidence, provenance, review status). It is clear on its own, but it does not distinguish this from a sibling like confirm_binding, which plausibly also touches review status.

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?

Usage is only implied: an agent can infer this is the tool for editing a binding after it exists, and confirm_binding/update_concept are the likely alternatives. There is no explicit when-to-use or when-not-to-use statement, and no prerequisites or exclusions are named.

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