Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_jgdy_tj_em

Read-onlyIdempotent

Retrieve institutional research survey statistics from East Money's data center for a given start date, providing structured data for financial analysis.

Instructions

东方财富网-数据中心-特色数据-机构调研-机构调研统计 https://data.eastmoney.com/jgdy/tj.html :param date: 开始时间 :type date: str :return: 机构调研统计 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo20220101
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the parameter is a start time and the return is a pandas DataFrame, but does not disclose pagination, rate limits, or the scope of the statistics.

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 text is compact, using a docstring-style format with source, URL, param, and return. However, it repeats the title information and includes a URL that may be of limited value to an agent.

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?

With no output schema, the description should explain what the returned DataFrame contains, but it only repeats '机构调研统计' without detail. It also does not clarify the date range behavior or how the statistics are aggregated.

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 schema has one parameter 'date' with zero description coverage. The description labels it as '开始时间' (start time), which adds some meaning, but does not specify the expected format (e.g., YYYYMMDD) or that it defaults to '20220101'.

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 identifies the tool as Eastmoney's institutional research statistics and includes the source URL. It specifies the resource and data type, though it lacks an explicit action verb and does not differentiate from the sibling tool stock_jgdy_detail_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?

No guidance is provided on when to use this tool versus alternatives. The description only states the data source and parameter, without any context about use cases, prerequisites, or exclusions.

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