Skip to main content
Glama
Sign In
FactorHub MCP Server

FactorHub MCP Server

by michaelfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_factors

Retrieve a list of financial factors filtered by category or keyword, showing factor code, name, category, annualized return, and Sharpe ratio.

Instructions

获取因子列表。支持按分类和关键词搜索。返回因子代码、名称、分类、年化收益、夏普比率等。

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": "list_factors"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
searchNo
pageNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses return fields (code, name, category, annualized return, Sharpe ratio) but omits behavioral traits such as pagination behavior, rate limits, or read-only nature. The description does not contradict any missing annotations.

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?

Two concise sentences in Chinese, no redundant information. Every sentence adds value: what the tool does, how to filter, and what is returned. Ideal length for quick comprehension.

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?

Given the existence of an output schema (not shown), the return field list in the description adds useful context. However, pagination behavior and parameter semantics are underspecified. The description is minimally adequate for a simple list tool but lacks guidance on handling result sets.

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 only mentions two parameters (category and search) but does not clarify their format, allowed values, or behavior. Pagination parameters (page, page_size) are ignored, leaving the agent without semantic guidance beyond parameter names.

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?

The description clearly states the tool retrieves a factor list with support for category and keyword search, and explicitly lists return fields (code, name, category, annualized return, Sharpe ratio). This distinguishes it from sibling tools like `get_factor_nav` or `get_factor_scores` which target specific factor metrics.

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?

The description mentions search capabilities (category and keyword), providing some usage context, but lacks explicit guidance on when to use this tool versus alternatives, or when not to use it. No prerequisites or exclusions are noted.

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