Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

kimi-websearch

Enter a question to get AI-powered web search results with cited answers.

Instructions

Kimi AI 联网搜索,输入问题返回AI搜索结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inquiryTextYes搜索问题

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states the basic function and that the result is an 'AI search result', but it does not describe the result format, whether sources are included, or any operational constraints or limitations. The agent is left guessing about the response structure.

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 one short, front-loaded sentence with no filler. It states the brand, the action, the input, and the output in compact form. Every word earns its place.

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?

For a single-parameter tool with no output schema, the description gives a high-level idea of input and output but not enough detail about the returned 'AI search result'. It also lacks usage context relative to sibling search tools, so it is minimally viable rather than complete.

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 the schema already documents inquiryText as '搜索问题'. The tool description simply restates that the user provides a question ('输入问题') without adding new meaning. This matches the baseline of 3 for high schema coverage.

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?

The description states a clear action and resource: 'Kimi AI 联网搜索' (Kimi AI online search) and the outcome '输入问题返回AI搜索结果' (input a question and return AI search results). It is specific enough to distinguish from video-downloader and feed tools, though it does not directly contrast with the sibling AI search tools like deepseek-websearch or doubao-websearch.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus the many sibling search tools. There are no exclusions, no mention of preferred scenarios, and no comparison to deepseek-websearch, doubao-websearch, toutiao-search, or other search-related siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/if530770/redfox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server