Skip to main content
Glama
Sign In
Agent中国通

Agent中国通

by FRANhss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

公开网页正文提取

cn_webpage_extract
Read-onlyIdempotent

Extract title, description, and summary text from a public web page. Blocks access to localhost and internal IP addresses to reduce SSRF risk.

Instructions

读取公开网页标题、描述和正文简摘。默认禁止访问 localhost/内网/保留地址，降低 SSRF 风险。

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": {
      "url": "<url>"
    },
    "name": "cn_webpage_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes公开 http/https 网页 URL
maxCharsNo最多返回正文字符数，默认 4000。
includeLinksNo是否返回前 30 个链接，默认 false。
includeMetadataNo是否返回更多 meta 信息，默认 true。
summaryModeNo正文模式，plain=纯文本，structured=分段。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint false, idempotentHint true, and openWorldHint true. The description adds valuable behavioral context about SSRF protection (blocking localhost/intranet). No contradictions. Could mention other behaviors like rate limits or error handling, but current info is sufficient.

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?

Two sentences, front-loaded with the core action. No unnecessary words. Very efficient.

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 rich schema and annotations, the description covers the main behavioral detail (SSRF protection). Some information like error handling or return format is missing, but for a read-only tool with openWorldHint, this is acceptable.

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?

All parameters are described in the schema (100% coverage). The description does not add extra detail beyond what the schema provides. 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?

The description clearly states it reads title, description, and body excerpt of public web pages. The sibling tools cover distinct domains (maps, video, weather, etc.), so this tool's purpose is well differentiated.

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 mentions default blocking of localhost/intranet/private addresses to reduce SSRF risk, providing context. It does not explicitly state when to use versus siblings, but the tool's purpose is clear enough.

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