Skip to main content
Glama
Sign In
ESCAP Data Explorer MCP Server

ESCAP Data Explorer MCP Server

by un-shayani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_indicators

Retrieve the full hierarchy of SDG and Thematic indicators from UNESCAP Data Explorer to browse and select an indicator for further data retrieval.

Instructions

Step 1: Retrieve the full hierarchy of available SDG and Thematic indicators from UNESCAP Data Explorer. Browse the results and choose ONE indicator. The indicator code is the segment after the last # in the 'val' field. Only use indicator codes returned by this tool — do not invent or source codes from elsewhere.

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": "get_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully explains behavior: retrieves full hierarchy, specifies output format (indicator code after last # in 'val'), and indicates it is a read operation. No annotations to contradict.

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?

Description is concise, front-loaded with purpose, and provides structured instructions. Every sentence serves a purpose without redundancy.

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 no output schema, the description fully explains output structure and usage. It also provides a critical constraint (do not invent codes), making it complete for the tool's context.

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?

Tool has no parameters, so baseline is 4. The description adds value by explaining how to use the output (extracting indicator code), though no parameter details are needed.

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 the tool retrieves the full hierarchy of SDG and Thematic indicators from UNESCAP Data Explorer, using specific verbs and resource. It distinguishes itself by instructing to browse and select one indicator, unlike sibling tools.

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?

Explicit step-by-step instructions are provided: use to browse, choose one indicator, extract code from 'val' field. It also warns not to invent codes, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools