Skip to main content
Glama

AutoTasker Hub — China Social Data API

wallstreetcn

WallstreetCN (华尔街见闻) 7x24 live financial newswire: headline + body + timestamp. $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": "wallstreetcn"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the feed is live 24/7, what fields are returned, and that the call costs $0.03 USDC. However, it omits behavioral details such as authentication or payment mechanics, rate limits, freshness semantics, and pagination behavior.

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?

The description is a single compact sentence that front-loads the source and resource, then lists returned fields and price. There is no redundant or filler wording.

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 low-complexity tool with one optional parameter and no output schema, the description adequately identifies the source, live nature, returned fields, and cost. It is incomplete because it never explains the limit parameter, and it provides no usage guidance or operational constraints.

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

Parameters1/5

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

The schema has one optional limit parameter with no description and 0% schema description coverage. The tool description never mentions the limit parameter, so it adds no meaning about what the parameter controls, valid range, or default behavior.

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 source, WallstreetCN (华尔街见闻), and a specific resource: a 7x24 live financial newswire returning headline, body, and timestamp. It is clear what the tool retrieves, though it does not explicitly differentiate itself from other financial or news-related siblings.

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 description implies a use case for live financial news but gives no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives. An agent must infer the appropriate context from the resource description alone.

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.