Skip to main content
Glama

AutoTasker Hub — China Social Data API

fx_rates

ECB reference FX rates via Frankfurter. CNY-friendly. $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": "fx_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoUSD
fromNoCNY
amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does add two genuinely useful facts — the ECB/Frankfurter data source and a stated cost of $0.01 USDC — but says nothing about rate freshness, rounding, error behavior for unsupported currencies, or whether amount is required for a conversion.

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

Conciseness3/5

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

Three short fragments with no padding, so nothing is wasted, but it is under-specified rather than front-loaded: the reader gets a source and a price before learning what the tool actually does.

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

Completeness2/5

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

With no annotations, no output schema, and no parameter documentation, the description is the only source of behavioral detail and it supplies source and cost but not the conversion semantics an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters. The description's only parameter-related signal is the vague "CNY-friendly", which weakly implies the from default, while to and amount are left entirely unexplained in both schema and description.

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

Purpose3/5

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

The description names the resource and data source ("ECB reference FX rates via Frankfurter") but never states the operation. With a from/to/amount schema this is evidently a currency conversion, yet the description never says "convert" or "get rate", so the agent must infer the verb from the schema.

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?

"CNY-friendly" hints that CNY is the intended default base, but there is no explicit when-to-use framing, no mention of when a sibling such as erapi_fx or btc_usd_rate would be preferable, and no statement of constraints such as supported currency codes.

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.