Skip to main content
Glama
Sign In
FactorHub MCP Server

FactorHub MCP Server

by michaelfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_valuation

Retrieve key stock valuation metrics including PE, PB, PS, dividend yield, market cap, and turnover rate for any A-share company by providing stock code and trade date.

Instructions

获取股票估值指标：PE、PB、PS、股息率、总市值、流通市值、换手率等。

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_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
ts_codeNo
trade_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as read-only status, authentication needs, or response format. It adds no value beyond the basic purpose.

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 a single concise sentence, front-loading the verb. However, it lacks structure (e.g., separating purpose from usage) and could be expanded with minimal additional detail.

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?

Given the absence of required parameters and presence of an output schema, the description should guide on output format or common parameter combinations. It does not, leaving the agent underinformed.

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?

Schema description coverage is 0%. The description does not explain the meaning of the two parameters (ts_code, trade_date), leaving the agent without guidance on how to specify them. The tool name offers a weak hint, but it is insufficient.

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 clearly states the tool retrieves stock valuation indicators (PE, PB, PS, etc.), providing a specific verb and resource. However, it does not distinguish from sibling tools like get_factor_nav or get_index_daily, which might have overlapping purposes.

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 on when to use this tool versus alternatives, no prerequisites or when-not-to-use conditions. The description only states what it does, leaving the agent to infer context.

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