Skip to main content
Glama

today_news

Read currently eligible reports from the same accepted news release as the website, with original publication/source dates, citations and revision identity. Historical articles remain in the archive. No live road or ski status.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent stories, 1-5 (default 1)

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?

No annotations exist, so the description carries the full burden, and it does real work: it discloses the returned payload (publication/source dates, citations, revision identity), and explicitly excludes historical articles and live road/ski status. It omits any statement about auth, rate limits, or fallback behavior when nothing is eligible.

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?

Three short sentences, front-loaded with the core scope statement followed by two boundary clarifications. The wording 'same accepted news release as the website' is slightly awkward but every sentence carries scoping information.

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?

A simple one-parameter read tool with no output schema, and the description compensates by describing what comes back and what is excluded. Nothing an agent needs in order to decide to call it is clearly missing, though routing to live_conditions stays implicit.

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% and the single 'limit' parameter already documents its 1-5 range and default of 1. The description adds no ordering or selection semantics for which 'recent stories' are picked, 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+resource: reads currently eligible reports matching the website's accepted news release, with dates, citations and revision identity. An agent can tell this is a news/report retrieval tool, but the phrase 'same accepted news release as the website' is idiosyncratic and doesn't name the sibling it differs from.

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?

'No live road or ski status' and 'Historical articles remain in the archive' implicitly bound when to use it and when not to, but the alternatives (live_conditions for live status, an archive path for old articles) are never named. Usage is inferable rather than stated.

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.

Resources