Skip to main content
Glama

get_answer_detail

Retrieve the full text of a Zhihu answer using question and answer IDs to read the complete answer.

Instructions

Read a full Zhihu answer.

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": {
      "question_id": "<question_id>",
      "answer_id": "<answer_id>"
    },
    "name": "get_answer_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
answer_idYes
question_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies read-only access via the verb "Read." It says nothing about authentication (notable given a check_login_status sibling exists), rate limits, whether private/deleted answers return errors, or what "full" includes such as images, comments, or vote counts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, which is good structurally. However, it is under-specified rather than appropriately sized for a two-parameter tool with zero schema coverage.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But with no annotations, 0% parameter coverage, and no usage guidance, the definition leaves too much for the agent to infer before a correct call can be made.

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

Parameters2/5

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

Schema description coverage is 0% and both question_id and answer_id are undocumented. The description adds no meaning at all about why both identifiers are required or what format they take, leaving the non-obvious two-ID requirement entirely unexplained.

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 gives a specific verb and resource ("Read a full Zhihu answer"), and the word "full" signals it returns complete answer content rather than a snippet or summary. The resource is distinguishable from siblings like get_article_detail and get_question_detail by the word "answer," though the description never explicitly routes the agent among those alternatives.

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 guidance, no prerequisites, and no mention of when to prefer a sibling such as search_content or get_question_detail. The agent must infer the use case entirely from the tool name.

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