Skip to main content
Glama
lpicci96

unesco-mcp

by lpicci96
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_indicators

Find UNESCO UIS indicators by combining text search with structured filters on theme and disaggregation to narrow results efficiently.

Instructions

Search UNESCO UIS indicators by relevance using text and structured filters.

Use this tool to discover which indicators exist for a topic. Results are capped (default 20, max 50) and intended for interactive exploration. For counting indicators with precise year or date filters, use count_indicators.

Suggested workflow for complex queries:

  1. Call list_themes to find the theme code if the user mentions a thematic area.

  2. Call list_disaggregation_types and get_disaggregation_values to find codes for concepts like "sex", "primary education", "age group". Do not pass these as the query parameter — use the structured filter parameters instead.

  3. Pass discovered codes as structured filters. Only use query for name-based narrowing after applying structured filters.

All provided filters are combined with AND logic. At least one filter must be provided. Results default to 20. If more exist, suggest narrowing with additional filters rather than increasing the limit.

Args: query: Full-text search on indicator name (supports stemming, e.g. "completing" matches "completion"). Secondary refinement only — do not use for concepts that map to themes or disaggregations. theme: Exact theme code (from list_themes). disaggregation_types: List of disaggregation type codes (from list_disaggregation_types). Indicators must support ALL listed types. disaggregation_values: List of disaggregation value codes (from get_disaggregation_values). Indicators must match ALL listed values. limit: Maximum number of results to return (default 20, max 50). Prefer narrowing filters over increasing limit.

Returns: A dictionary with: - "indicators": List of matching indicators, each with: code, name, theme, timeLine_min, timeLine_max. - "query_matches": Number of indicators matched by this query. This is NOT the total count of all UNESCO indicators — it only reflects how many matched these specific filters. Some relevant indicators may be missing if the query is too narrow or the text search didn't capture them. - "returned": Number of indicators included in this response (may be less than query_matches if truncated). - "hint": Guidance on next steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
themeNo
disaggregation_typesNo
disaggregation_valuesNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

No annotations provided, so description fully covers behavior. Discloses result capping (default 20, max 50), interactive exploration intent, and that query_matches is not total count. Warns that some indicators may be missing if query is too narrow. Describes return structure, ensuring agent knows what to expect.

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?

Description is lengthy but well-structured with purpose, usage, suggested workflow, filter logic, and parameter details. Every sentence adds value. Slight redundancy in parameter descriptions could be trimmed, but overall efficient given complexity.

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?

Covers all aspects: tool purpose, when to use, complex workflow, parameter semantics, output schema explanation (though output schema provided externally), and edge cases (truncation, query_matches vs total count). Adequate for the complexity of the tool.

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?

Schema has 0% description coverage, so description compensates fully. Each parameter gets detailed guidance: query (stemming, secondary refinement), theme (exact code from list_themes), disaggregation types/values (reference to other tools, must work for ALL), limit (default 20, max 50, prefer narrowing filters).

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?

Description clearly states it searches UNESCO UIS indicators using text and structured filters. It distinguishes from sibling tool count_indicators by noting the latter is for counting with precise year/date filters, making the scope specific and unambiguous.

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 states when to use (discover indicators) and when not (use count_indicators for precise counting). Provides a detailed suggested workflow for complex queries, guiding agents to find theme and disaggregation codes from other tools and to use structured filters before query parameter.

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/lpicci96/unesco-mcp'

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