Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_board_industry_name_ths

Read-onlyIdempotent

Fetch the complete list of THS industry board names and links from 同花顺. Returns a structured DataFrame to support financial market analysis.

Instructions

同花顺-板块-行业板块-行业 http://q.10jqka.com.cn/thshy/ :return: 所有行业板块的名称和链接 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type (pandas.DataFrame), which is useful, but it does not disclose any additional behavioral traits such as pagination, network dependencies, or data freshness, which are relevant for this type of tool.

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 description is very brief, consisting of just three lines: title line, URL, and return description. It is concise and front-loaded with the resource name. The inclusion of the URL and return type is efficient, but the lack of a verb sentence makes it slightly fragmented.

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

Completeness4/5

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

For a zero-parameter tool with no output schema, the description adequately specifies the output (all industry sector names and links) and the data structure (pandas.DataFrame). It is sufficient for an agent to know what to expect, though it could mention the scope of industries or time-freshness.

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?

The tool has zero parameters, so the baseline is 4. The description's mention of '所有行业板块的名称和链接' clarifies what the returned data contains, which is helpful even though there is no input schema to elaborate.

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 that the tool returns all industry sector names and links from 同花顺 (THS), with an explicit URL. The verb is implicit (return/list) but the output is unambiguous. It distinguishes itself by the THS source and the 'industry' category, but does not explicitly differentiate from sibling tools like stock_board_industry_name_em.

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?

There is no guidance on when to use this tool versus alternatives such as East Money (EM) or THS concept boards. The description implies it is for industry sector listings but fails to provide context for selection among the many board-related sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevynf/akbridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server