Skip to main content
Glama

The Veil Press: Breaking News and Desk

Get a breaking story

get_breaking_story
Read-onlyIdempotent

One breaking story by slug: full text (markdown and plain text), update log, numbered sources (primary or reported), images and url.

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": {
      "slug": "<slug>"
    },
    "name": "get_breaking_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe story slug from list_breaking_stories, e.g. treasury-two-year-auction-clears-at-4-708-percent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing what the payload contains — both text formats, an update log, sources tagged as primary or reported, and images — which is the main thing an agent needs to know before calling, absent an output schema.

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 compact sentence with the key differentiator and the return contents front-loaded; nothing is padded. The parenthetical and comma-list make it slightly dense but no sentence is wasted.

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-param read tool with no output schema, the description does the necessary work of enumerating return fields, which is where an agent would otherwise be blind. Minor omissions remain: no mention of behavior when the slug is unknown or whether the update log is truncated.

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 slug parameter is already documented with a concrete example in the schema. The description contributes nothing beyond restating 'by slug', 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 a specific verb-and-resource pair ('One breaking story by slug') and enumerates what it returns: full text in markdown and plain text, update log, numbered sources, images, url. This separates it from list_breaking_stories (a list) and search_stories (a search), though it never explicitly contrasts itself with the general get_story sibling.

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: 'by slug' plus the schema note that the slug comes from list_breaking_stories hints at the retrieve-after-list flow. There is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing this over the sibling get_story for non-breaking content.

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.