yimu-mcp

get_currency

get_currency

Fetch supported currency data for a user's account, enabling accurate multi-currency entries and clear financial records.

Instructions

查询币种数据（GET /currency/getCurrencyData/{userId}）。

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

Input Schema

Name	Required	Description	Default
`user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

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 full behavioral disclosure burden. It does disclose the HTTP method GET and the path, implying a read-only operation. However, it does not mention authorization requirements, whether user_id is required, return value structure, or error behavior.

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 description is a single compact sentence with no filler. It front-loads the operation and efficiently encodes the endpoint, so every part earns its place.

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?

For a simple one-parameter GET tool, this is minimally viable, but with no output schema the description should explain what '币种数据' actually includes and what the response looks like. It also lacks usage context to help an agent choose it among many sibling tools.

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?

The schema has one user_id string with 0% description coverage, so the description must compensate. The endpoint path /currency/getCurrencyData/{userId} adds that user_id is used as a path parameter, which is beyond what the schema states. It does not clarify whether the parameter is required, its format, or its exact meaning.

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 states '查询币种数据' (query currency data) and gives the exact GET endpoint, so the verb and resource are clear. It does not explicitly differentiate this tool from sibling get_* tools, but the resource is specific enough to avoid serious ambiguity.

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?

There is no guidance on when to use this tool versus alternatives such as auth_status, get_sts, or get_me. The only usage signal is the phrase 'query currency data', which is essentially implicit in the tool name and provides no decision support.

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