Skip to main content
Glama
Sign In
Agent Search MCP

Agent Search MCP

by lennney
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fetch_csdn_article

Read-onlyIdempotent

Retrieves full content from a CSDN blog article using its URL. Designed for Chinese developer blog posts on blog.csdn.net.

Instructions

Fetch content from a CSDN blog article.

Best for: Chinese developer blog content on CSDN. Not recommended for: Other Chinese sites — use free_extract instead.

@readOnly true @idempotent true — makes outbound HTTP requests to the CSDN 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": {
      "url": "<url>"
    },
    "name": "fetch_csdn_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS article URL on blog.csdn.net

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.2.0
  2. Removedv3.1.2
  3. Addedv3.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds 'makes outbound HTTP requests to the CSDN article URL', confirming the network call. This adds context beyond annotations, but does not introduce new safety concerns.

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?

Three succinct sentences with no wasted words. Front-loads the core purpose, then usage guidelines, and then behavioral notes. Highly efficient.

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

Completeness3/5

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

No output schema exists, yet the description does not specify what format the fetched content returns (e.g., plain text, markdown). This is a notable gap, though the tool is simple with one parameter.

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% with the url parameter well-described. The tool description does not add further meaning beyond the schema, so 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?

Clearly states 'Fetch content from a CSDN blog article.' and distinguishes from siblings by specifying it is for CSDN and not for other Chinese sites, with an alternative tool named (free_extract).

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

Usage Guidelines5/5

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

Provides explicit 'Best for' and 'Not recommended for' guidance, including a specific alternative tool. This directly helps an agent decide when to use this tool.

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