Skip to main content
Glama

Autario

by com.autario
OverviewDiscussionsAdmin

pct_change

Read-onlyIdempotent

Period-over-period percentage change for an indicator. Use for growth rates (YoY, QoQ, MoM) | "how fast did German GDP grow", "what is US CPI doing month over month". Runs on any verified autario indicator (World Bank, FRED, Eurostat, OECD, IMF, WHO, ECB, US Census, SEC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoReturn the full raw time series (heavy, many tokens). Default false → you get only the summary/stats, which is enough to ANSWER a question. Set true only when you must plot or export every point.
timeNoOptional time window. "2010-2023" keeps 2010 through 2023, "2019-01-2024-06" works by month, and a single "2015" keeps 2015 onward. Omitted or unparseable = the whole series.
entityYesEntity the series is read for: an ISO 3166 alpha-3 country code such as "DEU" or "USA", or an aggregate code such as "WLD" or "EUU" (the canonical name matches too). Use the codes list_indicators and get_entity_profile accept.
periodNoyoy | qoq | mom (default: yoy)
indicatorYesIndicator id of a numeric series, exactly as list_indicators or get_entity_profile return it (a public indicator or one of your own uploads or connector tables).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / entity / description
      Added value: +"Entity the series is read for: an ISO 3166 alpha-3 country code such as \"DEU\" or \"USA\", or an aggregate code such as \"WLD\" or \"EUU\" (the canonical name matches too). Use the codes list_indicators and get_entity_profile accept."
    • addedInput schema / properties / indicator / description
      Added value: +"Indicator id of a numeric series, exactly as list_indicators or get_entity_profile return it (a public indicator or one of your own uploads or connector tables)."
    • addedInput schema / properties / time / description
      Added value: +"Optional time window. \"2010-2023\" keeps 2010 through 2023, \"2019-01-2024-06\" works by month, and a single \"2015\" keeps 2015 onward. Omitted or unparseable = the whole series."
  2. Changed1 schema field changed
    • addedInput schema / properties / full
      Added value: +{
+  "description": "Return the full raw time series (heavy, many tokens). Default false → you get only the summary/stats, which is enough to ANSWER a question. Set true only when you must plot or export every point.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful scope context (works on any verified autario indicator, listing providers), but discloses nothing about computation details, edge cases, or what happens with sparse series.

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?

Front-loaded with the core purpose, followed by usage cues and then source coverage. The provider enumeration (World Bank, FRED, Eurostat...) is somewhat list-heavy but still serves the scope claim; overall it is tight and readable.

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?

For a 5-parameter read-only computation with no output schema, the description plus a fully documented schema cover the essentials — what it computes, when to use it, and which data sources apply. The schema's 'full' description handles the return-shape question, so the description need not repeat it.

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 description coverage is 100%, so the schema already documents entity, indicator, period, time, and full in detail. The description adds no parameter-level meaning beyond what is in the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific computation (period-over-period percentage change) applied to a specific resource (an autario indicator), which is far more precise than a generic 'calculate'. It does not, however, distinguish itself from siblings like calculate, compare_entities, or rolling_stats, so an agent still has to infer which statistical tool applies.

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?

The description gives clear use context — 'Use for growth rates (YoY, QoQ, MoM)' — reinforced by concrete example questions ('how fast did German GDP grow'). It stops short of naming exclusions or the alternative tool to pick when you want levels rather than changes.

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

All Autario 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