Skip to main content
Glama

NS Pros MCP Gateway

newswire-com__newswire_com_search_releases

Keyword/company search over Newswire.com's current newsroom feed (source: newswire.com). Matches against headline and sub-headline excerpt. Searches only the live rolling 50-item window each call, not a historical 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": {
      "query": "InHand Networks"
    },
    "name": "newswire-com__newswire_com_search_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches to return, 1-50 (default 20).
queryYesCompany name or keyword to match.

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?

With no annotations, the description carries the full load and does well: it discloses that matching is against headline and sub-headline only, and that each call sees just a rolling 50-item live window rather than an archive — a critical limitation an agent could not otherwise infer. It omits result ordering, pagination, and any rate/auth constraints, which keeps it from a 5.

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 short sentences, zero filler, and the key constraint about the rolling window is front-loaded alongside the purpose. 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?

For a simple two-parameter search with no output schema and no annotations, the description covers scope, matching surface, and the most important limitation. What is missing — result ordering and how a 50-item window interacts with limit — is minor rather than blocking.

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 coverage is 100% for both parameters, including the 1-50 range and default for limit, so the schema does the heavy lifting. The description adds only marginal meaning by clarifying what the query string is matched against (headline/sub-headline), which is a baseline-3 contribution.

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/company search over Newswire.com's current newsroom feed, matching headline and sub-headline excerpt. The scope clause ('live rolling 50-item window... not a historical archive') implicitly separates it from archive-oriented siblings, though no sibling is named 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 gives a meaningful boundary — search the live window only, not historical data — which lets an agent rule this tool out for archival queries. However, it never states when to prefer this over browsing tools like latest_releases or get_release, so the routing decision is only partially guided.

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.