Skip to main content
Glama

notfiction: is it real?

Real or Fiction? daily game

real_or_fiction_game
Read-only

Today's Real or Fiction? game: five headlines, some real news and some from satire sites. Returns the headlines (not the answers) and the link to play.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 safety is covered. The description adds real behavioral value by disclosing what is returned — headlines and the play link — and explicitly what is withheld ('not the answers'), which prevents an agent from expecting a solved result.

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?

A single sentence that front-loads the resource, then the content composition, then the return shape. No filler, no restatement of the tool name beyond what is needed for context.

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?

With no output schema, the description carries the burden of describing the return, and it does: five headlines plus a play link, with answers excluded. The only minor gap is whether the game rotates daily or whether repeated calls within a day return identical content.

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 zero parameters, so the baseline is 4. There is no parameter to mis-describe, and the description correctly signals a no-input, fetch-today's-game call.

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 resource ('Today's Real or Fiction? game') and exactly what it delivers ('five headlines, some real news and some from satire sites'). The daily-game framing and the mention of satire sites distinguish it cleanly from the news-reading siblings like search_news or top_stories.

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?

The word 'Today's' implies a once-per-day retrieval and the 'link to play' hints the caller uses it to hand off to a user, but there is no explicit when-to-use or when-not-to-use statement relative to check_claim or get_story. Usage is inferable rather than specified.

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