Skip to main content
Glama

notfiction: is it real?

Who broke it first

newsroom_track_record
Read-only

Which newsrooms break stories first that others then confirm. With no newsroom: the 30-day ranking. With a newsroom name: its 90-day record and recent scoops.

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

Input Schema

NameRequiredDescriptionDefault
newsroomNoOptional, e.g. "BBC News", "Fox News", "TMZ".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 real value beyond them by disclosing that the returned content differs by mode — a 30-day cross-newsroom ranking versus a 90-day record plus recent scoops — which is not derivable from the annotations or 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 short sentences, no filler, with the core purpose front-loaded and the mode behavior following immediately. Every clause carries information an agent would otherwise have to guess.

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 one-optional-parameter read-only tool with no output schema and annotations covering safety, the description covers both invocation paths adequately. It is slightly thin on the return payload — 'recent scoops' leaves the count and time horizon of those items unspecified.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above that: it explains the behavioral consequence of supplying or omitting the single parameter, mapping it to different time windows and result shapes. It stops short of noting whether partial or fuzzy newsroom names are accepted, which matters given only example strings in the schema.

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?

Names a specific resource and metric — newsrooms that break stories first and get confirmed by others — and immediately distinguishes the two operating modes (global ranking vs. per-newsroom record). An agent can tell this apart from search_news or get_story without opening any schema.

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 description makes the selection condition explicit: omit the newsroom for the aggregate 30-day ranking, supply one for a 90-day per-newsroom record. It gives clear context but no exclusions or contrast with named siblings such as get_story or top_stories.

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