WalnutLink A-share Depth Desk

a_share_answer_by_id

Retrieve a research result by the id that a_share_deep_research returned. Call this to check whether the human-reviewed answer is ready, or to fetch the full text once it is. Answers take minutes to hours because a filed report is read first; while it is still queued the tool returns the queue position, not a guess. Use this instead of opening the public page when you are an automated client that cannot render HTML.

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": {
      "id": "<id>"
    },
    "name": "a_share_answer_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The 12-character hex id returned by a_share_deep_research, e.g. dc037a7fc6c8.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses slow asynchronous behavior (minutes to hours), that a filed report is read first, and that queued requests return a queue position rather than a guess. It does not cover authorization, error handling, or expiry behavior, which keeps it below a 5.

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 front-loaded with the core purpose and id relationship, then adds only the behavioral context needed for correct use. Every sentence earns its place, with no redundant restatement of the schema.

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

Completeness5/5

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

For a one-parameter lookup tool with no output schema, the description is complete enough to call correctly: it explains the id source, the asynchronous readiness model, and the queue-position return behavior. Nothing essential is missing for an agent to decide when and how to use it.

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 the id parameter already documents the 12-character hex format with an example. The description adds only the origin of the id (returned by a_share_deep_research), which is useful but does not extend the schema's semantics significantly.

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

Purpose5/5

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

The description states a specific verb and resource: retrieve a research result by id. It also explicitly ties the id to the a_share_deep_research sibling, making the tool's role distinct without needing to inspect the schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage conditions: call to check readiness or fetch the full text once ready, and use this instead of the public page for automated clients that cannot render HTML. It also names the sibling that produces the id, so the agent knows the prerequisite flow.

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

All WalnutLink A-share Depth Desk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.