Skip to main content
Glama

notfiction: is it real?

Full coverage of a story

get_story
Read-only

Everything about one story: every outlet reporting it in the order they published (with links), who was first and who confirmed it, the facts the coverage agrees on, where outlets differ, and claims only one outlet makes.

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": {
      "id": "<id>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe story id from another tool, or its notfiction.com/s/<id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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's real contribution is the detailed inventory of returned content — valuable because there is no output schema — but it says nothing about missing stories, unconfirmed-later corrections, or response size.

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?

One sentence, front-loaded with 'Everything about one story,' followed by a compact enumeration where each item carries information. The result is a long but non-redundant sentence; slight readability cost for the list-in-prose format.

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 single-parameter read tool with no output schema, the description fully covers what an agent receives. Remaining gaps are edge behavior (unknown id, partial coverage) and not the core content, which is spelled out.

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 100% and the single parameter already documents that the id comes from another tool or a notfiction.com/s/<id> link. The description adds no further meaning about the id, so the baseline 3 applies.

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 the exact resource ('one story') and enumerates the returned content: outlets in publish order with links, first/confirming outlet, agreed facts, disagreements, and single-source claims. It is clearly a retrieval-by-id tool, but it never distinguishes itself explicitly from siblings such as check_claim or search_news.

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?

Usage is only implied through the parameter note that the id comes 'from another tool,' suggesting a follow-up step after discovery. There is no explicit when-to-use statement and no exclusion such as preferring check_claim for verifying an individual claim instead of pulling full coverage.

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