Skip to main content
Glama
kimi-search-mcp
by Wildare-98

Kimi Web Fetch

kimi_fetch

Fetches a single HTTP/HTTPS web page and returns its title and Markdown content, letting you read a specific URL after a search.

Instructions

Fetch a single HTTP/HTTPS web page with Kimi and return its title and Markdown content. Use after kimi_search to read a specific URL. Subject to site availability, access controls, and Kimi security policy.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTP/HTTPS URL to fetch. Must not contain a username or password.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return shape (title + Markdown) and important failure modes ('site availability, access controls, and Kimi security policy'), which is real behavioral value. However, it says nothing about content truncation, redirect handling, authentication/paywalled pages, or rate limits, leaving material gaps for a network-facing tool.

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?

Three short sentences, front-loaded with the operation and its result, then usage context and constraints. No padding, though the trailing policy sentence is vague enough that it earns only partial credit.

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?

This is a simple single-parameter read tool with no output schema, and the description still covers what it does, what it returns, and the external conditions that can cause failure. Missing details are secondary (content length limits, redirects) rather than blockers for correct invocation.

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?

There is one parameter and schema coverage is 100%: the schema already specifies 'HTTP/HTTPS URL to fetch. Must not contain a username or password.' The description adds no extra meaning about the URL parameter, so the baseline 3 for full schema coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch a single HTTP/HTTPS web page'), names the engine ('with Kimi'), and declares the return payload (title and Markdown content). It is distinguishable from kimi_search/kimi_search_pro through the 'read a specific URL' framing, though the differentiation only appears in the second sentence rather than in the core statement of purpose.

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?

'Use after kimi_search to read a specific URL' gives clear workflow context and implies the search-then-fetch pattern. It stops short of an explicit exclusion (e.g. do not use this to discover URLs, use kimi_search for that), so the agent must infer the negative case.

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