Skip to main content
Glama

notfiction: is it real?

Search the news

search_news
Read-only

Search current and recent news stories by person, place, topic or headline words. Each result says how many independent newsrooms reported it (the newsroom score), who reported it first, and links to the original reporting.

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": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesNames, places or a few headline words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that it is a read-only operation, and the description adds useful behavioral detail by saying it searches current/recent news and returns newsroom score, first reporter, and links to original reporting. It still does not explain recency windows, ranking, or source coverage limits, but the result-shape disclosure is meaningful given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences with no wasted wording. The purpose is front-loaded, and the second sentence earns its place by describing result contents in the absence of an output schema.

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?

For a simple two-parameter search tool with no output schema, the description covers the search domain, query types, and key returned fields. It omits explicit sibling routing and limit semantics, but the core information needed to invoke and interpret the tool is present.

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 explains that query accepts names, places, or headline words, and the description adds 'topic' as an additional query category. The limit parameter is not described in the description, though the schema provides its type, default, minimum, and maximum.

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?

The description states a specific verb and resource: search current and recent news stories by person, place, topic, or headline words. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as top_stories, get_story, or check_claim.

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?

It implies usage by describing the kinds of queries the tool accepts, but gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives. An agent can infer it is for keyword/entity news searches, but routing between sibling tools is left to context.

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.

Resources