Skip to main content
Glama

洋葱财报OnionData-MCP

查询维度与指标字典

get_dimensions
Read-onlyIdempotent

获取报表与指标目录(financial statement catalog):可用报表 income 利润表、balance 资产负债表、cashflow 现金流量表、predict 业绩预告,以及各指标中文名、单位、是否比率与 repotype(basic 基础指标 / operation 运营指标)。是调用 company_records 前的机器可读字典。本工具不计积分。需要 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": "get_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reponameNo只返回指定报表下的指标
repotypeNobasic / operation

Output Schema

NameRequiredDescriptionDefault
metricsYes
reportsYes
repotermsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful non-schema facts: no credit cost and an API Token requirement. It says nothing further about response shape or limits, but with an output schema present and strong annotation coverage that is a modest gap.

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?

The definition is dense but front-loaded: purpose and contents come first, then the workflow role, cost, and auth note as short trailing clauses. Nearly every clause carries information, with only mild redundancy between the report enum listing and the schema.

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?

With an output schema present, the description need not explain return values, and it covers the key agent-facing concerns: what is returned, when to use it relative to company_records, cost, and authentication. What remains thin is explicit guidance on choosing between this tool and similar catalog-style siblings.

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 coverage is 100% and both parameters are enum-constrained with their own descriptions, so the schema does the heavy lifting. The description does gloss the enum meanings in Chinese (income=利润表, basic=基础指标, operation=运营指标), adding some interpretive value, but not much beyond the schema's own enum labels.

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 names a specific verb and resource (fetch the report/indicator catalog) and enumerates concrete contents: income/balance/cashflow/predict reports plus Chinese names, units, ratio flags, and repotype. That is far more specific than a restated title, though it does not explicitly distinguish itself from the sibling list_indicators.

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?

It states a clear use context — that this is the machine-readable dictionary to consult before calling company_records — which tells an agent where this tool fits in a workflow. It gives no explicit when-not-to-use cases or direct comparison to alternatives, so it stops short of a 5.

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