Skip to main content
Glama

The Veil Press: Breaking News and Desk

Search Veil Press stories

search_stories
Read-onlyIdempotent

Keyword search across every Veil Press breaking story and Desk piece (headline, summary, tags and full text). Returns the best matches with url, published time, a snippet and a cite_as line.

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": {
      "query": "<query>"
    },
    "name": "search_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results (1-25, default 8).
queryYesWords to search for, e.g. "City of London Corporation" or "Treasury sanctions Iran".
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.6/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety burden is covered. The description adds useful behavior beyond that: which fields are indexed and what the response contains (url, published time, snippet, cite_as). It says nothing about result ordering semantics beyond "best matches" or how snippets are chosen, which keeps it at adequate rather than rich.

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?

Two sentences, zero filler: the first covers scope and indexed fields, the second covers return shape. Front-loaded with the verb and resource, and nothing is repeated from the schema.

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 correctly compensates by listing the returned fields, and it defines the corpus being searched. For a four-parameter search tool that gap is nearly closed; the only omission is any note on result ordering or what happens when nothing matches.

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%, with every parameter documented including examples for query and the enum for section, so the schema does the heavy lifting. The description adds only the broad notion of keyword matching across full text, with no detail on matching behavior, stemming, phrase handling, or how limit interacts with ranking.

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 ("Keyword search across every Veil Press breaking story and Desk piece") and enumerates the searched fields (headline, summary, tags, full text), which distinguishes it in spirit from the list_*/get_* siblings. It stops short of naming those siblings explicitly, so the differentiation is inferred 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?

The phrase "keyword search" implies the tool is for term-based retrieval rather than browsing, and "every ... story" implies no pre-filtering. However, there is no explicit guidance on when to prefer this over list_stories or get_story, nor any exclusion or prerequisite statement.

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.