Skip to main content
Glama

list_concept_mappings

Read-onlyIdempotent

List mappings between internal Variables and external vocabulary terms in forward or reverse direction, so you can find which Variables map to a term and vice versa.

Instructions

List concept mappings forward (by Variable) or in reverse (by external term).

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_concept_mappings"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNorestrict to one external term — with `vocabulary` this is the reverse lookup ("which Variables map to SP.POP.TOTL?")
concept_idNorestrict to one Variable
vocabularyNorestrict to one external vocabulary

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still contributes the non-obvious semantic that the tool performs a bidirectional lookup — a reverse index by external term — which is behavioral context an agent would not get from the annotations alone.

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?

A single front-loaded sentence with zero filler; the forward/reverse distinction is the first and only thing conveyed. Nothing redundant or padded.

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

Completeness4/5

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

With an output schema present and full parameter descriptions, the description needn't explain return values, and the directionality is covered. The one gap is that all three parameters are optional and the description never says what an unfiltered call returns, which matters for a list tool with zero required inputs.

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 explains term, concept_id, and vocabulary, including the term+vocabulary reverse-lookup combination. The description restates the Variable/external-term dichotomy but adds no syntax, format, or precedence detail beyond the schema, 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 uses a specific verb and resource ('List concept mappings') and adds a distinguishing axis (forward by Variable vs. reverse by external term). It does not explicitly name or contrast with siblings such as record_concept_mapping or list_concepts, so it falls short of full sibling differentiation.

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 forward/reverse framing implies which parameter to reach for depending on the lookup direction, which is useful implied guidance. However, there is no explicit statement of when to use this versus alternatives, nor what happens when no parameters are supplied (all mappings returned?).

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