Skip to main content
Glama

record_concept_mapping

Idempotent

Assert that a data variable maps to an external vocabulary term, capturing relation, confidence, provenance, and review status for governed concept mapping.

Instructions

Assert that a Variable maps to an external vocabulary term.

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": {
      "concept_id": "<concept_id>",
      "vocabulary": "<vocabulary>",
      "term": "<term>",
      "relation": "<relation>"
    },
    "name": "record_concept_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesthe external identifier or code, e.g. SP.POP.TOTL or Q148
relationYesSKOS mapping property — exact / close / broader / narrower / related
reviewedNomark the assertion as reviewed
concept_idYesVariable (concepts.id) being mapped
confidenceNo0..1; below the review threshold it is flagged pending review
provenanceNoregistry / manual / llmmanual
vocabularyYesexternal vocabulary, e.g. datacommons / worldbank / wikidata / xbrl-us-gaap / sdmx

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 this is a non-destructive write (readOnlyHint=false, destructiveHint=false) that is idempotent, and "Assert" is consistent with an upsert semantic. Beyond that the description adds nothing: it does not say what happens when a conflicting mapping already exists, how review flags or confidence thresholds are handled, or what side effects occur, even though the confidence/reviewed parameters hint at a review workflow.

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 zero filler, which is structurally clean. For a seven-parameter mutation tool it is arguably too terse rather than wasteful, but that shortfall is better attributed to completeness than to verbosity.

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 need not be explained, and annotations cover the safety profile. Still, for a seven-parameter write tool that creates reviewable assertions, the description omits conflict/overwrite behavior, required preconditions, and the review lifecycle, leaving real gaps for an agent deciding how to call it.

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% and each of the seven parameters carries its own documentation, including the SKOS relation set and the confidence threshold behavior. The description only restates that the subject is a Variable and the target an external vocabulary term, adding no meaning beyond the schema; 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?

"Assert that a Variable maps to an external vocabulary term" gives a specific verb and resource, and the write-oriented framing distinguishes it from list_concept_mappings or update_concept. It stops short of explicitly naming the sibling it differs from, so the differentiation is implied rather than stated.

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?

There is no when-to-use guidance, no mention of alternatives for reading or editing existing mappings, and no prerequisites such as whether the Variable or vocabulary must already exist. The agent must infer all routing from the single sentence.

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