Skip to main content
Glama

洋葱财报OnionData-MCP

搜索公司

search_companies
Read-onlyIdempotent

搜索 A 股上市公司(China A-share company search):按 6 位证券代码(ticker)、公司简称或拼音首字母匹配,返回最多 10 条 {scode, sname},供后续取数确定证券代码。truncated=true 表示结果已截断,请细化关键词。本工具不计积分。需要 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": {
      "query": "<query>"
    },
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes证券代码、简称或拼音首字母

Output Schema

NameRequiredDescriptionDefault
noteNo
queryYes
resultsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a hard result cap of 10, the exact response fields {scode, sname}, the meaning of the truncated flag, that calls are not billed ('不计积分'), and that an API Token is required. These are operational facts an agent cannot get from the structured fields.

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 front-loaded with purpose, then matching rules, then output shape, then caveats, with no filler paragraphs. The bilingual gloss and the 'not billed' note are mildly extraneous but each sentence carries operational value.

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

Completeness5/5

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

For a single-parameter search tool with an output schema already present, the description supplies the matching semantics, the 10-result cap, truncation handling, auth requirement, and cost note. An agent has everything needed to call it correctly and interpret a truncated response.

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?

Schema coverage is already 100% with a documented query parameter, so the baseline is 3. The description adds genuine detail by specifying that ticker input must be a 6-digit code and that pinyin initials are an accepted form, which tightens how the single argument should be formatted.

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 ('搜索 A 股上市公司') and specifies the matching keys (6-digit ticker, short name, pinyin initials), result cap, and returned fields. It also frames the tool's role as resolving a security code for later data retrieval, which distinguishes it from data-fetching siblings like company_records, though no sibling is named explicitly.

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 clearly states the use context ('供后续取数确定证券代码') and gives an actionable recovery path when results are truncated ('请细化关键词'). It does not name an alternative tool or state when not to use it, so it falls 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