Skip to main content
Glama

notfiction: is it real?

Today’s briefing

news_briefing
Read-only

A short briefing: the ~10 biggest stories that 3+ newsrooms are reporting, each with the facts their coverage agrees on. Good for "what's going on today?"

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds useful behavior beyond that, notably the ~10 item cap and the 3+ newsroom consensus criterion that shapes what is returned. It does not state the recency window behind 'today' or whether results are cached, which would matter for time-sensitive questions.

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 sentences, front-loaded with what the tool returns and the selection rule, then the use case. No filler or redundancy.

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 zero-parameter, read-only tool with no output schema, the description covers what comes back and why it is trustworthy (multi-newsroom agreement). The only real gap is temporal specificity, since 'today' and 'biggest' are left undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline applies; there is nothing for the description to disambiguate. It correctly presents the tool as a zero-argument call rather than implying filters that do not exist.

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 gives a concrete noun (a short briefing of ~10 top stories) and quantifies the selection rule (3+ newsrooms reporting, facts their coverage agrees on), which is specific enough to distinguish it from a plain story list. It does not name any sibling such as top_stories or search_news, so differentiation is by described behavior rather than explicit routing.

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

Usage Guidelines4/5

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

The closing line 'Good for "what's going on today?"' supplies a clear use context an agent can match against a user's vague current-events question. There is no when-not guidance and no named alternative for cases like a targeted topic lookup or a single-story fetch.

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