Skip to main content
Glama

The Veil Press: Breaking News and Desk

Get a story

get_story
Read-onlyIdempotent

One Veil Press story (Breaking or Desk) by slug or URL: full text (markdown and plain text), numbered sources, confirmed facts for breaking stories, url and cite_as.

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

Input Schema

NameRequiredDescriptionDefault
slugYesA slug from search_stories or list_stories, or a full story URL such as https://www.theveilpress.com/desk/what-is-the-city-of-london-corporation/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value by disclosing the response contents (markdown and plain text, numbered sources, confirmed facts, url, cite_as) despite there being no output schema. It stops short of noting lookup-failure behavior or any access constraints.

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 front-loaded sentence with a colon-delimited payload list; every clause (route shape, format, sources, breaking-only facts, url, cite_as) carries information an agent needs. Nothing is padded or repeated.

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 one-parameter read tool with no output schema, the description covers the important gap by specifying return fields, and annotations cover the safety profile. Missing only edge-case behavior (invalid slug, missing story) and any note on how confirmed facts differ for Desk stories.

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?

There is one parameter at 100% schema description coverage, which already explains that the slug can come from search_stories or list_stories or be a full URL. The description's 'by slug or URL' merely restates that, adding no format or validation detail beyond the schema. 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?

The description gives a specific verb+resource ('One Veil Press story ... by slug or URL') and enumerates what it returns: full text, numbered sources, confirmed facts, url, cite_as. It implicitly distinguishes itself from search_stories/list_stories by being the full-record fetch and from get_breaking_story by covering both 'Breaking or Desk', but that division of labor is left implicit rather than stated.

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: naming the returned payloads (full text, sources, confirmed facts) suggests 'call this once you have a slug and need the whole story'. There is no explicit when-to-use or when-not-to-use statement, and no route back to get_breaking_story or search_stories when this tool isn't the right one.

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.