Skip to main content
Glama
Sign In

JiZhiMCP

by io.github.alanwang100
OverviewDiscussionsAdmin

网页内容抓取

web_fetch
Read-onlyIdempotent

抓取指定 URL 网页并提取正文纯文本（去脚本/样式/标签）。Example: {"url":"https://example.com","max_chars":3000}

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://example.com",
      "max_chars": 3000
    },
    "name": "web_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes完整 URL（含 http:// 或 https://）
max_charsNo返回正文最大字符数，默认 3000，上限 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "max_chars": 3000,
+    "url": "https://example.com"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds real behavioral value by disclosing that output is main-body plain text with scripts, styles and tags stripped — a transformation the agent could not infer from annotations alone. It stops short of disclosing timeouts, redirect/auth behavior, or what happens on truncated or failed fetches.

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

Conciseness4/5

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

One compact sentence that front-loads the action, followed by an example. The example is redundant against the schema's examples field, which is the only wasted space; no other filler.

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?

Two parameters, one required, 100% schema coverage, rich annotations and no output schema — so the description need not explain return values. What it says is sufficient to invoke the tool correctly; only edge-case behavior (truncation signaling, fetch failures, dynamic content) is left unaddressed.

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%, so both parameters (url with required http/https form, max_chars default 3000 / cap 10000) are already fully documented. The description adds no semantics beyond the schema — the embedded example merely repeats the schema's own examples array. Baseline 3.

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 names a specific verb (抓取) and resource (指定 URL 网页), and further specifies the transformation: extracting main-body plain text with scripts/styles/tags removed. That is precise enough that an agent can distinguish it from every sibling (search/query/lookup tools) without opening 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 Guidelines3/5

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

Usage is only implied by the tool's nature — nothing states when to prefer it over a search tool, nor when NOT to use it (e.g., JS-rendered pages, authenticated or paywalled content, non-HTML resources). With no comparable sibling the routing risk is low, but the guidance is inferred rather than stated.

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

All JiZhiMCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources