Skip to main content
Glama

Latest news

latest_news
Read-onlyIdempotent

Lists the newest posts on theaftermath.news, newest first. Optional topic filters posts by tag (episodes are omitted when a topic is given).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items (capped at 20).
topicNoOnly posts carrying this tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral detail beyond them: results are ordered newest first, and episodes are silently omitted whenever a topic is supplied — a filtering side effect an agent could not predict from the schema.

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, with the core behavior front-loaded and the conditional edge case second. Nothing is repeated from the schema or annotations.

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 two-optional-parameter read-only listing tool with full schema coverage and annotations, this is nearly complete: ordering and the topic/episode interaction are both disclosed. Only the shape of the returned items is unstated, which is minor given the simple, obvious payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description earns an extra point by clarifying that topic matches a tag and, crucially, that supplying it changes the result set by dropping episodes. The limit parameter is left entirely to the schema, which already documents the cap.

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?

"Lists the newest posts on theaftermath.news, newest first" gives a specific verb (lists), a specific resource (posts), and the ordering. It implicitly separates itself from search_news by emphasizing recency rather than querying, though it never names the sibling explicitly.

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 description implies the browse-latest use case and notes that topic narrows results, but it never states when to prefer this over search_news or get_post. The agent must infer the routing from the words "newest" and "search" alone.

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