Skip to main content
Glama

AgentSearch Web Search

agentsearch_web_search
Read-onlyIdempotent

Search the web with AgentSearch and return the response as pretty-printed JSON text. Use this when you have a query and need hits rather than a page body; if you already have a URL, use agentsearch_extract instead (or agentsearch_render for JavaScript-heavy pages). Free, no wallet: this remote server uses the AgentSearch free relay. Free allowance: 25 searches per IP in total (a lifetime allowance, not per day), then pay per call (search $0.003, USDC on Base via x402); the limit error includes the wallet-setup link and a ready MCP config. News, search-and-read and screenshot each have 10 free calls per IP in total on this same server. Read-only: not destructive, but it uses the network. Integers for max_results outside 1-5 are clamped (default 5), not rejected.

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": {
      "query": "<query>"
    },
    "name": "agentsearch_web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or a natural-language question to search for (at least 2 characters).
max_resultsNoHow many hits to request (1-5, default 5). Values outside that range are clamped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantial context beyond them: a lifetime 25-search free allowance per IP (explicitly not per day), per-call pricing and payment rail, what the limit error contains, and the separate 10-call allowances on sibling tools. It also discloses that max_results out of range is clamped rather than rejected, which is real behavioral detail an agent needs before calling.

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?

Front-loads purpose and routing before cost details, and every clause is functional. The pricing/free-allowance passage is dense and somewhat extended for a two-parameter read tool, but it is decision-relevant rather than filler, so the minor length cost is justified.

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

Completeness5/5

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

For a two-parameter read-only search tool with full schema coverage and no output schema, the description covers routing, cost/quota limits, payment path, and parameter edge-case handling. Nothing an agent needs to invoke it correctly or recover from a limit error is missing.

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?

The schema already documents both parameters at 100% coverage, including the 1-5 range and clamping. The description's clamping note merely restates the schema, and it adds no new meaning for 'query' or syntax hints. With the schema carrying the load, baseline 3 is correct.

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?

Opens with a specific verb+resource ('Search the web with AgentSearch') and immediately constrains the return ('pretty-printed JSON text'). It explicitly distinguishes itself from agentsearch_extract and agentsearch_render, so an agent can pick it without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this when you have a query and need hits rather than a page body; if you already have a URL use agentsearch_extract, or agentsearch_render for JavaScript-heavy pages. That is when-to-use, when-not-to-use, and named alternatives in one sentence.

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.