Skip to main content
Glama
Sign In
FactorHub MCP Server

FactorHub MCP Server

by michaelfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_stock_info

Retrieve basic information for a single stock, including name, industry, listing date, and market sector.

Instructions

获取单只股票基本信息：名称、行业、上市日期、市场板块等。

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": {
      "ts_code": "<ts_code>"
    },
    "name": "get_stock_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
ts_codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Description only lists output fields without disclosing behavioral traits such as error handling, data freshness, or prerequisites. Since no annotations exist, the description should provide this context but fails to do so.

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?

Description is a single, efficient sentence that directly conveys purpose. No redundant information.

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

Completeness2/5

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

Despite having an output schema, the description lacks crucial context: no usage guidelines, no error handling info, no authentication requirements. For a simple tool, more completeness is expected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The required parameter 'ts_code' is not explained in the description. While its name suggests a stock ticker, the format (exchange suffix, numeric range) is not specified. With 0% schema description coverage, the description should clarify parameter semantics but fails to do so.

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?

Description clearly states it retrieves basic information for a single stock, listing specific fields (name, industry, listing date, market sector), which differentiates it from sibling tools like get_stock_list (list all stocks) and get_market_daily (daily trading data).

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?

Description provides no usage guidelines, such as when to prefer this tool over siblings like get_stock_list or get_valuation. It does not specify prerequisites or context for use.

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