Skip to main content
Glama

AgentSearch (hosted, free)

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. 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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description still adds real operational context: a 25-search lifetime free allowance per IP, then paid calls at $0.003 via x402/USDC on Base, and that the limit error carries a wallet-setup link and ready MCP config. The only waste is the "Read-only: not destructive, but it uses the network" clause, which restates the annotations nearly verbatim rather than extending them.

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-loaded with purpose and the routing decision, then pricing and edge cases, which is the right ordering. It is dense but nearly every clause carries information; the redundant read-only sentence and stacked parentheticals are the only drag.

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?

No output schema exists, and the description compensates by naming the return form (pretty-printed JSON hits) and covering the cost/limit path an agent needs before calling. What remains unspecified is the shape of the hit objects themselves, which a caller may still need.

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 coverage is 100%, so both parameters are already documented in the schema itself. The description's clamping note ("Integers for max_results outside 1-5 are clamped (default 5), not rejected") duplicates the schema's own wording rather than adding new meaning. Baseline 3 is right when the schema does all the semantic work.

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?

States a specific verb and resource ("Search the web with AgentSearch") plus the output form ("pretty-printed JSON text"). It also draws a clean line against agentsearch_extract and agentsearch_render, so an agent can pick without opening any schema.

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 both an inclusion condition ("when you have a query and need hits rather than a page body") and explicit alternatives with the condition that selects each: use agentsearch_extract if you already have a URL, agentsearch_render for JavaScript-heavy pages. That is the full when/when-not/alternatives pattern.

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.