Skip to main content
Glama
jpazvd

unicefstats-mcp

by jpazvd

Search UNICEF Indicators

search_indicators
Read-onlyIdempotent

Search UNICEF child development indicators by keyword. Returns indicator codes, names, and categories for further data retrieval.

Instructions

Search UNICEF child development indicators by keyword.

Returns indicator codes, names, and categories. Use the returned code values with get_indicator_info() or get_data(). Always start here if you don't know the indicator code.

Examples: "mortality", "breastfeeding", "education", "child labour", "stunting"

v1.1.0 advisory layer (additive to v0.9.0/v1.0.0 ambiguity_flag):

  • If response carries requires_confirmation=True, STOP and ask the user to disambiguate before calling get_data.

  • If response carries recommended + next_step, the model SHOULD call next_step verbatim (e.g. get_indicator_info(code='...')).

  • assistant_guidance is a plain-English directive (<200 chars).

  • Decision order: curated-ambiguous -> curated-preferred -> confident match -> none (wire-equivalent to v1.0.0). See internal/v1.1.0_design/ for rationale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of indicator candidates to return.
queryYesNatural-language search query (e.g. 'under-5 mortality', 'stunting', 'IMR', 'modelled estimates'). Accepts acronyms, common synonyms, and methodology phrases.
offsetNoPagination offset — skip this many top-ranked matches before returning. Use with `limit` to page through long match lists (e.g. limit=20, offset=0 for page 1; offset=20 for page 2). The response envelope carries `has_more` and `next_offset` so the LLM can decide whether to keep paging.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds substantial behavioral details about the advisory layer, including requires_confirmation and next_step, which are crucial for correct agent behavior.

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?

Well-structured with main purpose, usage, examples, and an advisory section. The advisory layer is detailed but necessary. Could be slightly more concise, but effective.

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 output schema and annotations, the description fully covers purpose, usage, pagination, and integration with sibling tools. No gaps for an agent to fail understanding.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions. Description adds context for the query parameter (natural-language, acronyms) and explains pagination logic beyond schema fields.

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?

Clearly states it searches UNICEF indicators by keyword and returns codes, names, and categories. Distinguishes from siblings by explaining how to use returned codes with get_indicator_info() or get_data().

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

Usage Guidelines4/5

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

Explicitly says 'Always start here if you don't know the indicator code.' Provides examples and integration guidance. Does not explicitly state when not to use, but the context is clear.

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