Skip to main content
Glama

洋葱财报OnionData-MCP

查询指标字典

list_indicators
Read-onlyIdempotent

获取财务指标字典(China A-share financial indicators dictionary):指标 key 到中文名与单位的映射,全市场统一口径,与公司无关。取数前用它确认 repoitem_key 与金额单位(元)。本工具不计积分。需要 API Token。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
unitsYes
indicatorsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive. The description adds context those fields cannot express: no credit cost ('本工具不计积分'), an API Token requirement, and that the dictionary is uniform across the market rather than per-company. It does not discuss response size or pagination, but the dictionary nature makes that low-stakes.

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-loads the resource definition, then the usage rule, then the cost/auth caveats in short clauses. The bilingual restatement adds length but little duplication of substance; nearly every clause carries distinct information.

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

Completeness4/5

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

For a zero-parameter dictionary lookup with an output schema, the description supplies what the schema cannot: what the mapping represents, that units are in 元, that it is market-wide, plus cost and auth notes. Nothing an agent needs to invoke it correctly appears to be 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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless, global lookup and adds meaning where it matters by explaining what the returned keys and units mean in practice.

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 ('获取财务指标字典'), and pins down the scope precisely: a key→Chinese-name+unit mapping that is market-wide and company-independent. The clause '与公司无关' lets an agent distinguish it from company-scoped lookup siblings 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 Guidelines4/5

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

Gives an explicit precondition for use: '取数前用它确认 repoitem_key 与金额单位(元)', which tells the agent to call this before fetching data. It does not name a competing tool or state when not to use this one, so it falls short of a full routing instruction.

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.

Resources