Skip to main content
Glama

Search402

Search402 preview

search_preview

Free web search preview: top 3 result titles and URLs from the Search402 index. For full results with snippets, call the paid x402 endpoint given by how_to_pay.

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": {
      "q": "<q>"
    },
    "name": "search_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the traits that matter most: the result is capped at 3 items, contains only titles and URLs (no snippets), and is free versus a paid tier. What it does not cover is rate limiting, authentication expectations, or failure behavior, which leaves a real gap for a network-backed search tool.

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?

Two sentences, no filler, and the output scope is front-loaded before the paid fallback. Every clause carries information an agent needs: cost model, result shape, result count, and the escape hatch.

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 one-parameter tool with no output schema and no annotations, the definition covers what is returned (titles and URLs, top 3), that it is free, and where to go for more. It is only missing operational details such as rate limits or what happens on an empty/no-result query.

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% for the single 'q' parameter, so the schema already documents it as the search query with a 300-character cap. The description adds no query syntax, operator, or encoding guidance beyond that, so this is the baseline 3.

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 gives a specific verb and resource ('Free web search preview') plus an explicit scope ('top 3 result titles and URLs from the Search402 index'), so the agent knows exactly what comes back. It also implicitly separates this tool from the paid full-results path, which is the only realistic confusion in this catalog.

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?

It names the alternative path explicitly and the condition that selects it: 'For full results with snippets, call the paid x402 endpoint given by how_to_pay.' That is a clear routing rule rather than just implied usage. It stops short of a fully symmetric when/when-not statement (it never says e.g. 'use this when you only need to identify candidate URLs'), so it falls one step short of the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources