Skip to main content
Glama

洋葱财报OnionData-MCP

查询报告期

list_report_periods
Read-onlyIdempotent

查询 A 股股票可用报告期(A-share report periods):先确认时间范围再取数。repoterm 决定口径——new 最新报告期(latest,默认)、quarter_t 单季度同比(single-quarter YoY)、quarter_h 单季度环比(single-quarter QoQ)、ttm 逐季度滚动四季合计(TTM)、year 年度(annual)。本工具不计积分。需要 API Token。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scode": "<scode>"
    },
    "name": "list_report_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
scodeYesA 股 6 位证券代码
repotermNo报告期口径:new 最新报告期(latest,默认)、quarter_t 单季度同比(YoY)、quarter_h 单季度环比(QoQ)、ttm 逐季度 TTM、year 年度(annual)new

Output Schema

NameRequiredDescriptionDefault
scodeYes
periodsYes
repotermYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Although annotations already declare this is a safe, read-only, idempotent operation, the description adds two important facts not in the annotations: the tool is free of credit cost (本工具不计积分) and requires an API Token. These are real operational constraints that an agent cannot infer from structured fields alone. It does not cover pagination or failure modes, but given the annotation coverage, the added value is solid.

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?

The description is front-loaded with the purpose, which is good, and the auth and credit notes are short. However, roughly half its length re-enumerates the repoterm enum already spelled out in the schema. That duplication is redundant and offsets the otherwise efficient structure.

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?

An output schema exists, so return values need not be explained, and the authorization and billing behavior are covered. For a two-parameter read-only lookup, what remains—mainly how to pick a repoterm for a given analysis goal—is a minor gap rather than a blocker.

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 100% description coverage, and the enum values for repoterm are already fully documented there. The description repeats those same definitions verbatim, including the default. This confirms the schema but adds no new meaning, such as when to choose one caliber over another, which is the baseline 3 case.

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 definition states a specific verb and resource: querying the available report periods for A-share stocks. The scope is clear enough that an agent can distinguish it from siblings like list_indicators or company_records. However, it does not explicitly contrast itself with any sibling tool.

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

Usage Guidelines3/5

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

'先确认时间范围再取数' implies a workflow position: confirm the time range before pulling data. This signals that the tool is preparatory, but it gives no explicit when-not conditions and names no alternative tool. Therefore, the usage guidance remains implied rather than stated.

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