Skip to main content
Glama

AutoTasker Hub — China Social Data API

tencent_quote

Tencent realtime quote with 5-level order book (bid/ask ladder), limit-up/down ready. Pass comma-separated codes like sh600519,sz000001. $0.03 USDC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "tencent_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated, e.g. sh600519,sz000001

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden. It does disclose two genuinely useful traits that structured fields do not: the payload includes 5-level order book and limit-up/down status, and each call costs $0.03 USDC (a paid operation). It omits auth requirements, rate limits, delayed-vs-realtime guarantees, and what happens with malformed or unknown codes.

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?

Three short, front-loaded sentences: payload contents first, then input format, then price. Nothing is buried or wasted, though the symbol-format sentence largely repeats the schema and could be trimmed.

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

Completeness3/5

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

For a single-parameter tool with no output schema and no annotations, the definition does substantial work by naming the returned fields and the per-call cost. It still leaves an agent guessing about market coverage, whether quotes are truly realtime or delayed, and failure behavior for invalid symbols.

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 description coverage is 100% and there is only one parameter, so the baseline is 3. The description's comma-separated hint and sh600519,sz000001 example duplicate what the schema property description already states, adding no new meaning such as exchange prefixes, batching limits, or case sensitivity.

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?

States a specific verb and resource: realtime Tencent quote enriched with a 5-level bid/ask ladder and limit-up/down flags. The scope (Chinese A-share symbol codes) is inferable from the examples, but it never names or contrasts with siblings such as quote_today or eastmoney_ashare, so differentiation is left to inference.

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?

The only instruction is a format hint ('Pass comma-separated codes like sh600519,sz000001'), which is calling syntax, not when-to-use guidance. There is no statement of when this realtime/order-book quote is preferable to the sibling quote or exchange-specific quote tools, and no exclusions.

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.