CurrencyCore

PPP analysis

analyze_ppp

Read-onlyIdempotent

PPP over time: how a country's purchasing-power-parity factor changed, comparing countries, or 'movers'. Growth plan or higher.

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

Input Schema

Name	Required	Description
`to`	No	Window end YEAR (e.g. 2024). Defaults to the current year.
`from`	No	Window start YEAR (e.g. 2015). Defaults to 10 years before `to`. See `period` for a shorthand.
`sort`	No	Movers ranking: increased (PPP factor rose most, default) or decreased.
`limit`	No	Movers: how many top results to return (default 10, max 200).
`stats`	No	Include min/max/avg of the PPP factor over the window per country. Defaults to true; pass false to skip.
`period`	No	Relative window shorthand for `from`: e.g. 10y, 20y, max. Ignored if `from` is given.
`countries`	No	Comma-separated ISO 3166-1 alpha-3 country codes to compare, e.g. IND,DEU,USA. OMIT to rank ALL countries by PPP-factor change ('movers' mode).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, so the bar is lower. The description adds a genuine non-schema fact: a plan-tier requirement ('Growth plan or higher'), which an agent cannot learn from annotations or schema. It does not describe the shape of results, but for a read-only analytical tool that is a minor gap.

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?

Two short sentences with no filler, and the core resource is front-loaded. The trailing 'Growth plan or higher' sentence is terse but earns its place as an access constraint.

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 7-parameter, all-optional tool with full schema coverage and no output schema, the description covers the analysis modes and the access tier; remaining detail is handled by the schema's per-parameter defaults. Only the return-value shape is unaddressed, which is acceptable here.

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% and every parameter (from/to/period/sort/limit/stats/countries) is already documented, including the 'OMIT countries to rank all' movers behavior. The description merely restates the movers-vs-compare distinction, adding no syntax, format, or default semantics beyond the schema.

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 resource and metric ('a country's purchasing-power-parity factor changed over time') plus the two analysis modes: cross-country comparison and 'movers' ranking. It does not name get_ppp_factor as the single-country alternative, so the differentiation from that sibling is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'comparing countries, or movers' implies the two use cases, and 'Growth plan or higher' gives an access precondition. There is no explicit statement of when to prefer this over get_ppp_factor (single-point lookup) or analyze_history, so routing must be inferred.

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

All CurrencyCore tools Inspect

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

Need Help?