Skip to main content
Glama
jpazvd

unicefstats-mcp

by jpazvd

Lookup UNICEF Indicator by Exact Code

lookup_by_code
Read-onlyIdempotent

Retrieve detailed metadata for a UNICEF indicator by providing its exact SDMX code. Designed for code-based lookups, not text searches.

Instructions

Strict canonical lookup of a UNICEF indicator by its exact code.

Use this INSTEAD of search_indicators when you already have a UNICEF indicator code (e.g. CME_MRY0T4, IM_DTP3, ED_15-24_LR). Do NOT pass natural-language descriptions, synonyms, or partial names — this tool is canonical-only.

Two-tool separation introduced in v0.9.0 to give the LLM a self-describing choice at tool-selection time:

  • have a CODE? → lookup_by_code(code)

  • have WORDS? → search_indicators(query)

Returns the same canonical metadata shape as get_indicator_info on success. On unknown code, returns an error with an explicit abstain_instruction directing the model to stop — NOT to fall back to search_indicators (which would re-enter the loop that 96% of v9 Arm B stuck queries hit).

Returns:

  • on success: {status: "ok", code, name, description, dataflow, sdmx_api, disaggregation_filters, ambiguity_flag: false, ...}

  • on unknown code: {status: "error", error, ambiguity_flag: false, abstain_instruction, tip}

  • on natural-language input mistakenly passed: {status: "error", error, abstain_instruction directing to search_indicators}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesExact UNICEF SDMX indicator code (e.g. 'CME_MRY0T4'). Same envelope as get_indicator_info — both route through a shared _build_indicator_envelope helper, so the disaggregation_filters block is literally identical across both tools.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses behavior on success and error, including abstain instructions to prevent fallback loops. Explains the rationale for two-tool separation and how the tool handles unknown codes vs. natural-language input. Annotations already confirm read-only and idempotent, so description adds valuable context without contradiction.

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?

The description is well-structured with clear sections, but is somewhat lengthy. However, every sentence adds value, and the front-loading of purpose and usage makes it efficient for an agent to parse.

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

Completeness5/5

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

Given the tool has one parameter, clear annotations, and an output schema (not shown but indicated), the description covers all necessary aspects: purpose, usage, behavior, error handling, and rationale. It is fully complete for an agent to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `code` is fully described in the schema with constraints and example. The description enhances this by providing exact code examples and specifying the canonical nature, adding meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Strict canonical lookup of a UNICEF indicator by its exact code,' specifying the verb, resource, and method. It differentiates from sibling tool `search_indicators` by emphasizing exact code vs. words.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises to use this tool instead of `search_indicators` when having a exact code, and warns against passing natural-language descriptions. Provides a clear decision rule: 'have a CODE? → lookup_by_code; have WORDS? → search_indicators'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jpazvd/unicefstats-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server