Skip to main content
Glama
RapierCraft

alterlab-mcp-server

by RapierCraft

alterlab_search

Search the web using multiple search engines with automatic failover. Optionally scrape result pages for full content, with filters for domain, time range, and safe search.

Instructions

Search the web, find information online, look up any topic, or research a subject across the internet. Returns search results with URLs, titles, and snippets from multiple search engines. Uses AlterLab's SERP engine with Google/Bing/DuckDuckGo multi-engine failover for reliable results. Costs $0.001 per search query. Set scrape_results=true to also scrape each result page (with anti-bot bypass) and get full content — each page is billed at its normal scraping tier cost. Use domain to restrict results to a specific site (equivalent to site: operator). Use time_range to filter by recency (hour/day/week/month/year). Use safe_search=true to filter adult content from results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page number (1-indexed). Page 2 returns results 11-20, etc.
queryYesSearch query (max 500 characters)
domainNoRestrict results to a specific domain (applied as site: prefix, e.g. 'docs.example.com')
countryNoISO 3166-1 alpha-2 country code for geo-targeted results (e.g., 'US', 'GB', 'DE')
formatsNoOutput formats when scrape_results=true
languageNoLanguage code for results (e.g., 'en', 'fr', 'de')
time_rangeNoFilter results by recency
num_resultsNoNumber of results to return (1-30)
safe_searchNoEnable safe search filtering to exclude adult content from results. Defaults to the search engine's own safe-search setting when omitted.
scrape_resultsNoIf true, scrape each result page and include content in response. Each page is billed at its scraping tier cost in addition to the base search fee.
extraction_schemaNoJSON schema for structured extraction when scrape_results=true
Behavior4/5

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

With no annotations, the description must cover behavioral traits. It discloses cost ($0.001 per query), multi-engine failover, anti-bot bypass on scrape, and billing for optional scraping. It does not mention rate limits or caching, but the disclosed information is substantial and free of contradictions.

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?

The description is a single dense paragraph that efficiently conveys purpose, behavior, cost, and parameter usage. It is front-loaded with the core function. While it could benefit from bullet points for readability, it remains concise without redundant information.

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 11 parameters, no output schema, and no annotations, the description is quite complete. It explains the search result contents, cost, optional scraping, and key parameters. It could briefly mention pagination (page parameter behavior) but that is covered in the schema. Overall, it provides sufficient context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining domain as 'site: operator', time_range for recency, safe_search for adult content filtering, and scrape_results for full page scraping. This exceeds the baseline by providing practical context.

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 the tool's purpose: 'Search the web, find information online, look up any topic, or research a subject across the internet.' It specifies the return format (URLs, titles, snippets) and distinguishes itself from sibling tools like alterlab_scrape by focusing on search rather than scraping a specific page.

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 provides guidance on when to use this tool by detailing its capabilities (multi-engine failover, cost, optional scraping). It explains parameter usage (domain, time_range, safe_search) but does not explicitly exclude use cases better served by sibling tools (e.g., alterlab_scrape for known URLs). However, the context makes the typical use case clear.

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/RapierCraft/alterlab-mcp-server'

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