Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_market_activity_legu

Read-onlyIdempotent

Retrieve market activity and profit-making effect analysis from Legu. Provides a pandas DataFrame with metrics to gauge market sentiment and investment opportunity.

Instructions

乐咕乐股网-赚钱效应分析 https://www.legulegu.com/stockdata/market-activity :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, idempotentHint, and destructiveHint=false, establishing it as a safe, read-only operation. The description adds that it returns a pandas.DataFrame and the source URL, which provides some value beyond annotations, though it does not elaborate on data scope or potential quirks.

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 and follows a clear docstring structure with :return: and :rtype:. However, the first line is redundant with the title, and the content is terse rather than informative. It earns a 4 for being compact and structurally clear.

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?

Without an output schema, the description is the only source for understanding the returned data. It states the return type is a DataFrame but does not describe columns, time range, or the meaning of '赚钱效应'. This leaves the agent without enough context to interpret the output or decide if it meets a user's need.

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?

There are zero parameters, so there is no parameter ambiguity to resolve. The schema coverage is effectively complete, and the description is not required to compensate for missing parameter documentation. Baseline 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely repeats the title '乐咕乐股网-赚钱效应分析' with no verb or explanation of what the tool actually computes or returns. It does not distinguish itself from sibling stock market tools, and the term '赚钱效应' (profit effect) is left undefined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. No scenarios, prerequisites, or exclusions are mentioned. The URL is useful for human reference but does not clarify selection criteria for an AI agent.

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