Skip to main content
Glama

Gastat Series

gastat_series
Read-onlyIdempotent

Fetch the full time series for a GASTAT indicator id (from gastat_search or gastat_headline), multiple periods for comparison over time, not just the latest value. Covers population, employment, GDP, consumer prices, trade indices, etc. Some indicators require a region/sector breakdown GASTAT does not expose through this call; those return a clear message rather than raw data, retry with a different indicator from gastat_search.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "indicator_id": "131"
    },
    "name": "gastat_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
recentNoMost recent periods to return (1-100, default 20).
indicator_idYesGASTAT indicator id, e.g. "131" (population by year) or "132" (population growth rate). From gastat_search or gastat_headline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real operational context beyond them: this returns a whole series rather than one value, and certain breakdown-dependent indicators return a clear message instead of raw data, with retry guidance.

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?

Three sentences, front-loaded with the verb and resource, followed by disambiguation and failure handling in priority order. The domain list ('population, employment, GDP, consumer prices, trade indices, etc.') is the weakest line, mildly expendable, but it does bound scope for an open-world tool.

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?

There is no output schema, so the description carries the return-value burden, and it does describe the return as a full multi-period series plus a documented failure mode. It omits shape details such as period granularity, units or ordering, which leaves a small but real gap for a data-retrieval tool.

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 both parameters are already documented, including the 1-100 range and default of 20 for 'recent'. The description reinforces that multiple periods are returned and points to where indicator_id comes from, but adds no new syntax, format or constraint detail. Baseline 3 applies.

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 opens with a specific verb and resource: 'Fetch the full time series for a GASTAT indicator id'. The clause 'multiple periods for comparison over time, not just the latest value' directly separates it from gastat_headline, so an agent can discriminate siblings without opening any schema.

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?

It states the selection context (historical comparison rather than a single latest value), names gastat_search and gastat_headline as the sources of valid ids, and gives a recovery path when an indicator needs a region/sector breakdown. It stops short of an explicit 'use X instead when you only want the latest value', leaving that to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.