CurrencyCore

PPP conversion factor

get_ppp_factor

Read-onlyIdempotent

Return the IMF World Economic Outlook PPP conversion factor for one country and year: local currency units per international dollar. Use when the user needs the raw multiplier for one country/year, for example a cost-of-living comparison. Use convert with ppp=true to price an amount, and analyze_ppp for change over time or a cross-country ranking. year defaults to the latest configured PPP year (2024). Returns { year, countryCode, pppFactor, projected }; projected: true marks an IMF projection rather than observed data. An unknown country or year is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "get_ppp_factor"
  }
}

Input Schema

Name	Required	Description	Default
`year`	No	Four-digit year. Defaults to the configured current PPP year (2024).
`country`	Yes	Country as an ISO 3166-1 alpha-3 code (e.g. IND).

Output Schema

Name	Required	Description	Default
`year`	Yes
`pppFactor`	Yes
`projected`	Yes
`countryCode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "countryCode": {
+      "type": "string"
+    },
+    "pppFactor": {
+      "type": "number"
+    },
+    "projected": {
+      "type": "boolean"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "countryCode",
+    "pppFactor",
+    "projected"
+  ],
+  "type": "object"
+}

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description still adds real behavioral context: 404 on unknown country or year, a signed-in connection requirement, and a per-call billing cost of 1 API request. It also explains the `projected` flag semantics, which is a genuine data-quality caveat. Only minor gap is no note on caching or rate limiting beyond the billing line.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight paragraph, front-loaded with the verb, resource and scope, then routing guidance, then defaults and return shape, then failure and auth/billing facts. No filler sentences and nothing repeated from the annotations.

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 two-parameter read tool this covers purpose, alternatives, defaults, return shape, error behavior, auth and cost. Even though an output schema exists, restating the returned fields and the `projected` flag adds interpretation value rather than redundancy.

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 coverage is 100%, so both parameters are already documented including the ISO alpha-3 format and the 2024 default. The description reinforces the default year and adds the meaning of the returned factor's unit, which helps the agent interpret the value rather than just pass it.

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 ("Return the IMF World Economic Outlook PPP conversion factor") and pins the scope to one country and year, with the unit defined as local currency units per international dollar. It explicitly separates itself from `convert` and `analyze_ppp`, so an agent can route correctly 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 Guidelines5/5

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

Gives a positive use condition ("needs the raw multiplier for one country/year, for example a cost-of-living comparison") and two named alternatives with the conditions that select them: `convert` with `ppp=true` to price an amount, `analyze_ppp` for time series or cross-country ranking. When-to-use and when-not-to-use are both covered.

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?