Skip to main content
Glama
Sign In
cn-scraper-mcp

cn-scraper-mcp

by goesByhc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zsxq_article

Fetch the complete content of a Knowledge Planet article using its direct URL, which is obtained from the topic's inline article link.

Instructions

获取知识星球文章全文。

article_url 来自 zsxq_topics 结果中的 topic 对象， 仅当 topic 类型为文章时可用（talk.article.inline_article_url）。

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": {
      "article_url": "<article_url>"
    },
    "name": "zsxq_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_urlYes文章 URL（从 topic 的 inline_article_url 字段获取）

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It accurately describes the operation as fetching full text, but does not disclose any potential side effects, rate limits, or error conditions. This is adequate for a simple read-only tool.

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 two sentences long, with the main purpose in the first sentence and additional context in the second. No unnecessary words, perfectly front-loaded.

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?

Given the presence of an output schema (indicated by 'Has output schema: true'), the description does not need to explain return values. It covers the prerequisite (topic type must be article) and the parameter source, making it complete for the tool's complexity.

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

Parameters4/5

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

The input schema has 100% description coverage for the one parameter (article_url). The description adds value by specifying the exact source of the URL (inline_article_url field of a topic object), which is not in the schema. This helps the agent understand where to obtain the parameter.

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 clearly states the tool's purpose: retrieving the full text of a knowledge planet article. It specifies the source of the URL (from zsxq_topics topic object) and the condition (topic type must be article), distinguishing it from sibling tools like zsxq_topics.

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

Usage Guidelines4/5

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

The description explicitly tells when to use this tool: when you have an article_url from zsxq_topics and the topic type is article. It does not mention alternatives or when not to use, but the context is clear enough for an agent to decide.

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