Skip to main content
Glama

notfiction: is it real?

Is it real?

check_claim
Idempotent

Check whether a rumor, headline, claim or link (X/TikTok/YouTube post, article) is being reported by real newsrooms. Compares it with what 37 newsrooms (BBC, NYT, Fox News, NPR, Guardian, CBS, NBC and more) are reporting now and have reported since November 2026, flags satire sites and old news, and returns a verdict, the matching coverage with links, and a public answer page. Use when a user asks "is this real?", "is this fake news?", or shares a link to check. It reports coverage; it is not a fact-check.

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": {
      "claim": "<claim>"
    },
    "name": "check_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe claim in plain words, a headline, or a link to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, and the description explains why: it returns 'a public answer page', disclosing a side effect the agent would otherwise not expect from a check tool. It also adds data-window and coverage details (37 named newsrooms, coverage since November 2026), satire detection and stale-news flagging, and the shape of the results.

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?

Front-loads the core check, then the corroboration mechanism, then usage triggers and the scope disclaimer; every sentence carries information. The newsroom roll-call ('BBC, NYT, Fox News, NPR, Guardian, CBS, NBC and more') is slightly padded but does establish source credibility.

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?

With no output schema, the description still tells the agent what comes back: a verdict, matching coverage with links, and a public answer page. Combined with the source scope and time window, an agent has enough to call it and set expectations.

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?

Only one parameter and the schema description already covers it at 100% ('claim in plain words, a headline, or a link'). The description echoes the same accepted input forms without adding format rules, URL handling, or behavior of the 500-character limit, so it adds little beyond 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?

States a specific verb and resource: checks whether a rumor, headline, claim or link is being reported by real newsrooms. The closing line 'It reports coverage; it is not a fact-check' cleanly separates it from fact-checking tools and from the sibling news-reading tools.

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?

Gives explicit trigger phrases ('is this real?', 'is this fake news?', shares a link) that map directly to user intent, plus a scope boundary excluding fact-check duty. It stops short of naming a specific alternative sibling to route to when the user wants general news rather than verification.

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