Skip to main content
Glama

There's An AI For That

Search news

search_news
Read-only

Search public AI news by keyword, time frame, topic, source, and importance. An omitted or empty query lists matching items.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNolatest
limitNo
queryNoOptional keywords matched against title, description, and topics. Empty lists all matching items.
sinceNoOptional inclusive lower date bound as YYYY-MM-DD, ISO 8601, or 24h, 7d, or 30d.
topicNoOptional exact topic name or slug.
untilNoOptional inclusive upper date bound as YYYY-MM-DD, ISO 8601, or 24h, 7d, or 30d.
sourceNoOptional publisher name, domain, or ingest source.
minimum_importanceNo

Output Schema

NameRequiredDescriptionDefault
newsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / news / items / properties / downvotes / description
      Added value: +"Number of TAAFT downvotes for this news item."
    • addedOutput schema / properties / news / items / properties / popularity / description
      Added value: +"Net TAAFT news votes: upvotes minus downvotes."
    • addedOutput schema / properties / news / items / properties / upvotes / description
      Added value: +"Number of TAAFT upvotes for this news item."
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are covered without description help. The description only adds "public" as a data-scope qualifier; it says nothing about pagination, result caps, or coverage of the underlying corpus, so it adds little behavior beyond the structured fields.

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?

Two short sentences, front-loaded with purpose followed by the empty-query rule, with no filler. The second sentence restates the schema's own query description almost verbatim, so it does not fully earn its place.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains missing for an 8-parameter tool at 63% schema coverage is the meaning of sort and limit, which the description never addresses.

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 63%, with query, since, until, topic, and source already documented in-schema. The description gestures at the same dimensions (time frame, topic, source, importance) but adds no format or semantics beyond the schema, and leaves sort and limit — both with defaults and a max of 50 — unexplained in either place.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Search public AI news") and enumerates the filter dimensions it supports (keyword, time frame, topic, source, importance), which is enough to place it among the search_* siblings. It never names or contrasts with get_news or the other search_* tools, so differentiation relies on the reader inferring the naming convention.

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

Usage Guidelines3/5

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

"An omitted or empty query lists matching items" is a useful when-to-use hint that tells the agent the query is optional and empty means browse rather than fail. There is no guidance on choosing this tool over get_news for a specific article, and no stated preconditions or exclusions.

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.