Skip to main content
Glama

AutoTasker Hub — China Social Data API

erapi_fx

160+ fiat exchange rates from a single base currency (exchangerate-api mirror, daily refresh). $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
baseNoUSD
symbolsNoOptional comma list, e.g. CNY,EUR,JPY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the data source (exchangerate-api mirror), refresh cadence (daily), and cost ($0.01 USDC), but it does not explain payment mechanics, authentication, rate limits, or whether the operation is strictly read-only. For a paid data-retrieval tool, those are meaningful gaps.

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?

The definition is two short sentences with zero waste. The core capability is front-loaded, and the source, refresh cadence, and price are compactly appended without disrupting readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with two optional parameters and no output schema, but the description does not describe the response shape or the behavior when symbols is omitted. It covers purpose, source, freshness, and price, which is helpful, but an agent would still need to infer some invocation semantics.

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 50%: the symbols parameter is documented in the schema, while base is not. The description partially compensates by saying rates come from a single base currency, which maps to the base parameter, but it does not explain the default base of USD or what happens when symbols is omitted.

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?

The description clearly identifies the resource as '160+ fiat exchange rates' and states the scope as 'from a single base currency.' It does not use a direct verb like 'fetch' or 'list,' but the intended operation is obvious. It also signals fiat-only coverage, which helps distinguish it from crypto-rate tools without relying on sibling names.

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

Usage Guidelines2/5

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

The description offers no explicit guidance on when to use this tool versus alternatives such as fx_rates or btc_usd_rate. It implies usage by saying it returns fiat exchange rates from a single base currency, but there are no when-not conditions, prerequisites, or alternative-routing instructions.

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.