Skip to main content
Glama
chestnutsheep

DeepFusion MCP Server

港股关键指标

stock_indicators_hk

Fetch essential financial metrics from Hong Kong stock reports using a 5-digit ticker symbol, helping investors assess company performance.

Instructions

获取港股市场的股票财务报告关键指标

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes5位港股代码,如 00700

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It weakly implies a read-only operation ('获取') but says nothing about data granularity, time period, formatting, rate limits, or any operational caveats. For a tool with zero annotation coverage, this is insufficient transparency beyond the obvious retrieval action.

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, direct sentence conveying the essential purpose without any redundant wording or filler. It is appropriately front-loaded with the action and target market.

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?

The tool is simple with one parameter and no output schema, so the description does not need to enumerate return values. However, in the context of a large sibling set with overlapping financial-data tools, the lack of comparative or usage context leaves an agent uncertain about scope and selection. It is minimally viable but not complete.

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 description coverage is 100% and the single parameter symbol is well-documented with a format hint ('5位港股代码,如 00700'). The tool description adds no new parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 a specific action ('获取') and resource ('港股市场的股票财务报告关键指标'), clearly indicating it fetches key financial indicators for Hong Kong stocks. The '港股' qualifier implicitly differentiates it from the sibling stock_indicators_us, though it does not explicitly name alternatives or define what counts as '关键指标'.

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?

No guidance is provided on when to use this tool versus closely related siblings like financial_indicators, financial_statements, or stock_indicators_us. An agent must guess which tool is appropriate for a given task based solely on the name and short description.

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

Deploy Server

Other Tools