Skip to main content
Glama

Un Sdg

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Series Data

get_series_data
Read-onlyIdempotent

Get observations for an SDG series in a geographic area over a time range. seriesCode comes from list_indicators/list_series; areaCode is an M49 code from list_geoareas. Returns { data: [...] } where each observation has value, timePeriodStart, geoAreaName, source, footnotes, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaCodeYesM49 geographic area code, e.g. "1" for World (from list_geoareas).
pageSizeNoMax observations to return (default 100).
seriesCodeYesSDG series code, e.g. "SI_POV_DAY1" (from list_indicators/list_series).
timePeriodEndNoOptional latest year, e.g. "2020".
timePeriodStartNoOptional earliest year, e.g. "2010".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "areaCode": "1",
+    "seriesCode": "SI_POV_DAY1"
+  },
+  {
+    "areaCode": "4",
+    "pageSize": 50,
+    "seriesCode": "SI_POV_DAY1",
+    "timePeriodEnd": "2020",
+    "timePeriodStart": "2010"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint. Description adds return format but does not discuss pagination behavior or rate limits beyond the schema's pageSize parameter. No contradiction with annotations.

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 two sentences covering purpose, parameter sources, and return shape. No extraneous information, though it could be slightly more structured.

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?

Given 5 parameters, 2 required, and no output schema, the description provides sufficient context: return shape, parameter source. It is complete enough to use the tool correctly.

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 coverage is 100%, so each parameter already has a description. The description adds context by linking seriesCode and areaCode to other tools and noting optional parameters. Baseline 3 is appropriate as description adds moderate value beyond 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?

Description clearly states the tool retrieves observations for an SDG series in a geographic area over a time range, with specific verb 'get observations' and resource 'SDG series'. It distinguishes from sibling tools by referencing list_indicators/list_series and list_geoareas for obtaining codes.

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?

Description explains when to use (when seriesCode and areaCode are available) and implicitly suggests prerequisite calls to list_indicators/list_series and list_geoareas. It provides clear usage context, though lacks explicit when-not-to-use or alternative tools.

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

All Un Sdg toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources