Skip to main content
Glama

AutoTasker Hub — China Social Data API

eastmoney_index

Mainland index snapshot: SSE Composite, SZSE Component, ChiNext, CSI300, STAR50 with change %. $0.02 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_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 one genuinely behavioral fact — the $0.02 USDC cost per call — and 'snapshot' implies a non-mutating read, but it says nothing about data freshness, market-hours behavior, rate limits, or error conditions for a paid call.

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?

One sentence, front-loaded with the resource and then the returned contents, with the price tacked on at the end where it belongs. Nothing is wasted, though 'with change %' is slightly cryptic about which field it annotates.

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, read-only snapshot tool with no output schema, the description covers what is returned and what it costs, which is most of what an agent needs. The remaining gaps — freshness/timing and response shape — are modest given the tool's simplicity.

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 takes zero parameters, which sets the baseline at 4. The description correctly implies there is nothing to configure — the index set and the change-% field are fixed — so no parameter meaning is missing.

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 the resource precisely — a mainland China index snapshot — and enumerates the five indices returned (SSE Composite, SZSE Component, ChiNext, CSI300, STAR50), which also implicitly separates it from the sibling eastmoney_ashare that covers individual stocks. It is clear what an agent gets back, though it never states a verb (fetch/get).

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 when-to-use or when-not guidance, and no alternative is named despite a closely related sibling (eastmoney_ashare) existing. The agent must infer from the word 'index' that this is the aggregate-market tool rather than the single-stock tool.

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.