CurrencyCore

PPP analysis (change, compare, movers)

analyze_ppp

Read-onlyIdempotent

Measure how a country's IMF PPP conversion factor changed over a year window: start/end year and factor, % change, and optional min/max/avg. Use for purchasing-power trends and cross-country PPP rankings. Omit countries to rank all countries (movers); provide ISO alpha-3 codes to compare specific ones. Use get_ppp_factor for a single country/year value, and convert with ppp=true to price an amount. Defaults: 10-year window, sort increased, limit 10, stats true. Returns { from, to, mode, stats, results[] }, with projected: true marking an IMF projection. Returns an error when no PPP data exists in the window. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

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).

Output Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`mode`	Yes
`sort`	No
`stats`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 11, 2026

addedInput schema / properties / sort / enum

Added value: +[
+  "increased",
+  "decreased"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "from": {
+      "type": "number"
+    },
+    "mode": {
+      "enum": [
+        "compare",
+        "movers"
+      ],
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "changePct": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "country": {
+            "type": "string"
+          },
+          "endFactor": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "endYear": {
+            "type": "number"
+          },
+          "note": {
+            "type": "string"
+          },
+          "projected": {
+            "type": "boolean"
+          },
+          "series": {
+            "additionalProperties": {
+              "type": "number"
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "startFactor": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "startYear": {
+            "type": "number"
+          },
+          "stats": {
+            "additionalProperties": false,
+            "properties": {
+              "avg": {
+                "type": "number"
+              },
+              "max": {
+                "type": "number"
+              },
+              "min": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "min",
+              "max",
+              "avg"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "country",
+          "startYear",
+          "endYear",
+          "startFactor",
+          "endFactor",
+          "changePct",
+          "projected"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sort": {
+      "enum": [
+        "increased",
+        "decreased"
+      ],
+      "type": "string"
+    },
+    "stats": {
+      "type": "boolean"
+    },
+    "to": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "mode",
+    "stats",
+    "results"
+  ],
+  "type": "object"
+}

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new operational context: requires a signed-in connection, needs Growth plan or higher, and bills 1 API request per successful call. It also discloses that `projected: true` marks IMF projections and that an error is returned when the window has no PPP data.

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 purpose, then mode selection, then alternatives, then defaults, then response/auth — a sensible ordering with no filler sentences. Slightly dense in places (restating return shape and defaults) that could be trimmed given the output schema and 100% schema coverage.

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?

For a 7-parameter, optional-args analysis tool with an output schema, the description covers mode selection, defaults, return shape, error behavior, auth/plan gating, and billing. Nothing an agent needs to invoke it correctly or set expectations is missing.

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?

Schema description coverage is 100%, so defaults and enum meaning are already documented; the description mainly restates the defaults (10-year window, `sort` increased, `limit` 10, `stats` true). Its added value is the cross-parameter mode semantics — that omitting `countries` flips the tool into movers ranking rather than comparison — which the schema alone does not make obvious.

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?

States a specific verb and resource — measure how a country's IMF PPP conversion factor changed over a year window — and enumerates what is returned (start/end factor, % change, optional stats). It explicitly separates itself from `get_ppp_factor` (single value) and `convert` (pricing an amount), so an agent can pick it without opening schemas.

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?

Gives explicit routing rules: omit `countries` to rank all countries in movers mode, provide ISO alpha-3 codes to compare specific ones, use `get_ppp_factor` for a single country/year, use `convert` with `ppp=true` to price an amount. It also states defaults and the error case when no data exists, leaving little to inference.

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?