Skip to main content
Glama

The Veil Press: Breaking News and Desk

List breaking stories

list_breaking_stories
Read-onlyIdempotent

Latest breaking stories from The Veil Press, newest first: title, slug, url, published time, summary, key fact, cover and share image URLs, tags and sources.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly stories with this tag (case-insensitive), e.g. Treasury.
limitNoHow many stories to return (1-50, default 10).
sinceNoOnly stories published after this ISO 8601 time, e.g. 2026-10-26T00:00:00Z.
include_archivedNoInclude stories older than 7 days (default true).

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, idempotentHint, destructiveHint=false and a closed world, so safety is covered structurally. The description usefully adds the sort order (newest first) and the exact fields returned, but says nothing about result volume, paging behavior, or what happens when no stories match.

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?

A single front-loaded sentence stating source, ordering, and payload. The field enumeration is long but earns its place given there is no output schema; nothing is redundant.

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, listing the returned fields is genuinely valuable and largely substitutes for it, and the ordering is stated. The remaining gap is behavioral: it does not clarify how many results come back by default, what the 7-day breaking window means, or how archived stories interact with 'latest'.

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 description coverage is 100%, so every parameter (tag, limit, since, include_archived) is already documented with examples and defaults. The description adds no parameter-level meaning, so the baseline of 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?

The description names a specific resource (breaking stories from The Veil Press) with a defined ordering (newest first), which distinguishes it from a general story listing. It does not, however, explicitly contrast itself with the sibling list_stories or get_breaking_story, leaving the boundary to be inferred from the name.

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 words 'Latest breaking' imply the use case (recent news retrieval), but there is no explicit when-to-use or when-not-to-use statement, and no alternative is named despite list_stories and search_stories being plausible alternatives. Nor does it explain the interaction between 'breaking' and the include_archived parameter.

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.