Skip to main content
Glama

The Veil Press: Breaking News and Desk

List latest stories

list_stories
Read-onlyIdempotent

Latest Veil Press stories, newest first, from Breaking, the Desk or both: headline, slug, url, published time, summary, tags, sources and cite_as.

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_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly stories with this tag (case-insensitive).
limitNoHow many stories (1-50, default 10).
sinceNoOnly stories published after this ISO 8601 time.
sectionNobreaking (news), desk (long-form reporting and history) or all (default).all

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, non-destructive and closed-world, so the safety profile is fully covered. The description adds ordering behavior (newest first) and enumerates the returned fields, which is useful beyond the annotations, but it says nothing about what the default 'latest' window is, result truncation, or empty-result behavior.

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: scope, ordering, section coverage, then the returned fields. It is dense and waste-free, though the colon-and-list fragment style makes the return-field enumeration read as a run-on rather than clearly separated clauses.

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 (headline, slug, url, published time, summary, tags, sources, cite_as) is genuinely valuable and fills that gap. Combined with ordering and section scope, the definition covers what an agent needs to call it, missing only a note on how far back 'latest' reaches and how results behave when filters match nothing.

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 each of the four parameters is already documented in the schema, including the section enum and defaults. The description maps section to concepts ("Breaking, the Desk or both") but adds no format, unit, or interaction detail the schema does not already carry, so 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?

Names a specific verb and resource ("Latest Veil Press stories") plus ordering ("newest first") and scope (Breaking, Desk, or both), so an agent can tell it retrieves a recent-stories feed. It does not name or explicitly distinguish itself from siblings like list_breaking_stories or search_stories, leaving that distinction to inference from the section parameter.

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: "latest ... newest first" signals recency browsing and the section parameter signals breaking-vs-desk coverage, which suggests search_stories is for querying rather than browsing. There is no explicit when-to-use, when-not, or named alternative, so the agent must infer the routing.

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.