Skip to main content
Glama

NS Pros MCP Gateway

newswire-com__newswire_com_latest_releases

Latest press releases from Newswire.com's public newsroom RSS feed (source: newswire.com, an Issuer Direct wire that shares many releases with ACCESS Newswire). Returns headline, published time and sub-headline excerpt for each release, newest first. Covers the 50 most recent releases, not Newswire.com's full archive.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "newswire-com__newswire_com_latest_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax releases to return, 1-50 (default 20).
since_hoursNoOnly return releases published within the last N hours (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the data source (public RSS), the exact fields returned (headline, published time, sub-headline excerpt), ordering (newest first), and a hard coverage ceiling of 50 releases with excerpt-only rather than full-text content. It omits refresh cadence and any failure/empty-result behavior, so not quite exhaustive.

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?

Three tight sentences with zero filler: source and coverage first, then returned fields and ordering, then the archive limitation. Each sentence contributes distinct 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?

No output schema exists, but the description compensates by enumerating the returned fields and ordering, and it bounds the result set. For a simple two-optional-parameter read tool this is nearly sufficient; only freshness/caching and empty-result behavior are left unaddressed.

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 both limit and since_hours are already documented in the schema. The description only echoes the 50-release cap that the limit parameter already encodes and says nothing about since_hours or default behavior, so it adds little beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource (latest press releases) and pins the exact source (Newswire.com's public newsroom RSS feed) plus the coverage boundary (50 most recent, not the full archive). An agent can immediately tell this is a 'recent feed' tool rather than an archive search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States clearly when this applies (the 50 most recent releases, newest first) and gives an explicit exclusion ('not Newswire.com's full archive'), which tells the agent to reach for something else for historical queries. It stops short of naming the alternative search tool, so routing still requires a small inference.

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.