Skip to main content
Glama

AgentSearch Search + Read

agentsearch_search_and_read
Read-onlyIdempotent

Search the live web and return the top pages as clean markdown in one call. Each result includes title, URL, snippet, domain and page text. Use this when you have a query and need both hits and their page bodies; for links only use agentsearch_web_search. Free, no wallet: this remote server uses the AgentSearch free relay. Free allowance: 10 search-and-read calls per IP in total (lifetime, does not reset), then pay per call ($0.005). Read-only: not destructive, but it uses the network. Page content is untrusted third-party data.

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_search_and_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or a natural-language question to search for (at least 2 characters).
max_charsNoMaximum markdown characters per page (1-20000, default 8000).
num_resultsNoHow many top results to read (1-5, default 3).
render_fallbackNoIf true, retry at most one empty or thin page in a headless browser (default false).

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 readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, yet the description adds genuinely new behavioral facts: a lifetime free allowance of 10 calls per IP that does not reset, a $0.005 per-call price afterward, no wallet requirement via the free relay, network usage, and a warning that page content is untrusted third-party data. The quota and trust warnings are things an agent cannot learn from structured fields and materially change how it should call the tool.

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 return shape, then usage routing, then cost/quota, then safety — a sensible order with no filler sentences. The 'Read-only: not destructive' clause largely restates the annotations, a minor redundancy, but the remaining sentences each carry information.

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?

There is no output schema, but the description compensates by listing the fields each result contains. Combined with the quota, cost, auth-free access and untrusted-content caveat, an agent has everything needed to decide and call correctly.

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%, so the schema already documents query, max_chars, num_results and render_fallback including ranges and defaults. The description only implies the count and length knobs via 'top pages' and 'page text', adding no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 live web and return the top pages as clean markdown in one call') and enumerates the return fields (title, URL, snippet, domain, page text). It also explicitly contrasts itself with the sibling agentsearch_web_search, so an agent can pick between them without opening either 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 an explicit selection rule: 'Use this when you have a query and need both hits and their page bodies; for links only use agentsearch_web_search.' That is a concrete when-to-use plus a named alternative with the condition that selects it.

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.