Skip to main content
Glama

AutoTasker Hub — China Social Data API

eastmoney_ashare

A-share quotes via Eastmoney: top gainers board, or one stock by code (e.g. 600519) with OHLC, volume, amount, PE. $0.03 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
symbolNoOptional 6-digit A-share code, e.g. 600519

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful behavioral context by declaring the paid cost ($0.03 USDC) and the data fields returned, but it is silent on failure behavior for an unknown code, whether the charge applies per call or per result, and any rate limits.

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?

A single front-loaded clause covers the resource, both modes, the returned fields, and the price, with no redundant wording. Nothing in the sentence could be removed without losing information an agent needs.

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-required-parameter read tool with no output schema, the description substitutes well by listing the returned fields and disclosing cost. The remaining gap is the unmentioned limit parameter and the behavior on an invalid symbol, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: symbol is documented in the schema with a 6-digit example, while limit has no description at all. The description usefully clarifies that symbol acts as a mode switch (single stock vs. board) rather than a filter, but it never mentions limit, so it only partially compensates for the coverage gap.

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 names a specific resource (A-share quotes via Eastmoney) and enumerates both operating modes: a top-gainers board or a single stock by code, plus the returned fields (OHLC, volume, amount, PE). An agent can tell what it gets without opening the schema. It does not explicitly differentiate itself from the sibling eastmoney_index, so it falls short of a 5.

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?

Mode selection is implied by the structure 'top gainers board, or one stock by code' — omit symbol for the board, supply a code for a single quote — but this is never stated as an instruction. There is no explicit statement of when to prefer this over eastmoney_index or of any preconditions, leaving usage to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.