Skip to main content
Glama
Sign In
404K Knowledge Planet MCP Server

404K Knowledge Planet MCP Server

by wlhtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

读取完整知识星球话题

zsxq_get_topic

Retrieve full topic content by ID: returns complete text, author segments, images, PDF/attachment links, and the original URL.

Instructions

按话题 ID 获取完整正文、分段作者、图片、PDF/附件本站地址和原文链接。

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": "zsxq_get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes话题 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It accurately describes the read operation and returned data but does not disclose potential errors, rate limits, or idempotency. Lacks depth but is not misleading.

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?

Single sentence, concise and to the point. No redundant information. Efficiently communicates the tool's function.

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?

Given the simple nature of the tool (one parameter, no output schema), the description adequately covers the return values by listing the types of data retrieved. It could mention if the response is structured or paginated, but is sufficient for a get-by-ID operation.

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 coverage is 100% with a single parameter 'id' described as '话题 ID'. The description does not add additional meaning to the parameter beyond the schema, but the overall tool purpose is clear. Baseline 3 is appropriate.

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?

Description clearly states the verb ('获取'), the resource ('话题'), and the specific data retrieved (complete content, segmented authors, images, PDF/attachment addresses, original link). It effectively distinguishes this from sibling tools which are for status, listing, and searching.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The need for a specific topic ID is implied by the required parameter, but there is no mention of when not to use it or references to sibling tools.

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

Deploy Server

Other Tools