Skip to main content
Glama
spider-rs

Spider MCP Server

by spider-rs

spider_ai_search

Search the web with AI-driven intent understanding and relevance ranking. Apply custom guidance to filter and rank results for precise information retrieval.

Instructions

AI-enhanced web search with intent understanding and relevance ranking. Requires an active AI subscription (https://spider.cloud/ai/pricing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoMax results
tbsNoTime range filter
promptNoAdditional AI guidance for filtering/ranking results
searchYesSearch query
countryNoTwo-letter country code
languageNoTwo-letter language code
return_formatNoOutput format. Default: raw
fetch_page_contentNoFetch full page content from results
Behavior2/5

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

No annotations provided; description only mentions AI enhancement and subscription. No disclosure of behavioral traits such as rate limits, error handling, or what the AI does beyond ranking. Minimal transparency.

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?

Very concise, one sentence plus a subscription note, no fluff. However, it could be slightly more informative while remaining concise.

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

Completeness2/5

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

Description is very brief given the tool has 8 parameters with no output schema. Does not explain how AI enhancement works, interaction between parameters, or return values. Lacks context for agent to fully understand usage.

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%, baseline is 3. Description does not add additional meaning to the parameters; it is a generic description without parameter-specific details.

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 it is an AI-enhanced web search with intent understanding and relevance ranking. Distinguishes from sibling tools like spider_search (basic search) and spider_ai_browser (browser). The mention of subscription requirement adds context.

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?

Explicitly notes that an active AI subscription is required, providing a link. Does not explicitly list when to vs. when not to use, but the tool's name and description imply use for AI-enhanced search vs. basic search.

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/spider-rs/spider-cloud-mcp-v2'

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