Skip to main content
Glama
1tylermitchell

Sairen

by 1tylermitchell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_web

Run web searches and SERP discovery without a browser or API keys. Get ranked results, canonical URLs, and snippets directly in MCP workflows.

Instructions

    [Cost: $0.0015 USDC on Base & Solana] Zero-browser web search and SERP discovery.
    Returns ranked results, clean canonical URLs, and snippets without requiring human API keys.

    Args:
        query: Target search query string (e.g. 'ethereum base l2 transaction fees').
        max_results: Maximum SERP results to return (1-20, default: 5).
        payment_signature: Optional x402 Base/Solana USDC transaction hash (defaults to developer mock key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the cost ($0.0015 USDC), the payment mechanism (optional x402 hash defaulting to developer mock key), and the return type (ranked results, URLs, snippets). However, it omits details on rate limits, pagination, error handling, or whether results are cached, which are relevant for a paid external call.

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 compact and informative, front-loading the cost and key purpose in the first sentence, then listing arguments. It avoids fluff but could be slightly tighter by integrating the args into the prose rather than a separate block.

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?

For a three-parameter tool with no output schema, the description covers the essential aspects: what it returns, parameter constraints, and cost/payment. It doesn't describe error responses or operational limits, but the core information an agent needs to invoke it correctly is present.

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

Parameters5/5

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

The schema has no parameter descriptions (coverage 0%), so the description is the sole source of semantics. It explains 'query' with an example, defines 'max_results' range (1-20, default 5), and clarifies 'payment_signature' is optional with a mock default. This fully compensates for the schema gap.

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 performs web search and SERP discovery, with a specific verb ('search') and resource ('web'), and specifies it returns ranked results, clean canonical URLs, and snippets. This distinguishes it from sibling tools like extract_web_markdown (which extracts content from a given URL) and classify_url, though it doesn't name them explicitly.

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

Usage Guidelines3/5

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

The description implies usage for web search queries and highlights the advantage of not requiring human API keys, but it does not explicitly state when to prefer this over alternatives like extract_web_markdown or classify_url. No exclusions or conditions are provided.

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