Skip to main content
Glama

AgentSearch News Search

agentsearch_news_search
Read-onlyIdempotent

Search recent news articles with AgentSearch and return them as JSON text: title, URL, snippet, domain and publish date. Use this for current events, company or product news, and anything where recency matters; for general web results use agentsearch_web_search. Free, no wallet: this remote server uses the AgentSearch free relay. Free allowance: 10 news searches per IP in total (lifetime, does not reset), then pay per call ($0.003). Read-only: not destructive, but it uses the network.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNews topic, company, person or event (at least 2 characters).
max_resultsNoHow many articles to return (1-10, default 5).

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?

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), it discloses the billing model: a lifetime free allowance of 10 news searches per IP that never resets, then $0.003 per call via the AgentSearch free relay. That cost/rate-limit detail is exactly the behavior an agent cannot get from structured fields, and it correctly reinforces rather than contradicts the read-only hints.

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 purpose and alternative are front-loaded and the pricing caveat follows logically, with no filler sentences. There is minor redundancy between "Free, no wallet" and "Free allowance," which keeps it short of a 5.

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 search tool with no output schema, the definition covers purpose, alternative routing, returned fields, network use, and the cost/quota model. Nothing an agent needs in order to decide whether and how to call it 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?

Schema description coverage is 100%, so both parameters (query, max_results) are already fully documented with length and range constraints. The description lists returned fields but adds no syntax, format, or interpretation guidance for the inputs, so baseline 3 applies.

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 opens with a specific verb and resource ("Search recent news articles with AgentSearch") and names the return shape (title, URL, snippet, domain, publish date). It also distinguishes itself from agentsearch_web_search, so an agent can pick it 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?

It states explicit triggers — current events, company or product news, anything where recency matters — and names the alternative (agentsearch_web_search) for general web results. The when-to-use and when-not-to-use conditions are both spelled out.

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.