Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__recent_changes

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple", change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT -> GNews fallback (news mentions in window, GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since acc

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": {
      "type": "company",
      "since": "30d",
      "value": "AAPL"
    },
    "name": "ntsb-investigations__recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start, ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the fan-out to three upstream sources in one parallel call, the GDELT->GNews fallback triggered by rate limits or 5xx, and a known soft-fail (PatentsView sunset May 2025). It stops short of describing the shape of the returned feed or per-source failure reporting.

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?

The core is a single dense sentence that front-loads the intent phrasing and then the source fan-out, with no filler. It is slightly overloaded with overlapping example phrasings and ends mid-word ('`since` acc'), which hurts polish but not comprehension of the main behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a fan-out aggregator with no output schema and no annotations, the description should say what the returned feed contains (per-source sections, timestamps, empty-source behavior). It explains where data comes from and how fallbacks work but not what the agent receives, which is a meaningful gap for this complexity level.

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%, so all three parameters are already documented, including the relative/ISO formats for `since` and ticker-vs-CIK for `value`. The description reinforces the window semantics ('last N days/weeks/months') but adds no format or edge-case detail beyond the schema, and the sentence covering `since` is cut off.

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?

The description states a concrete verb and resource: a change feed for a company over the last N days/weeks/months, aggregated from SEC EDGAR, GDELT/GNews, and USPTO. It is clearly a multi-source recent-activity lookup rather than a generic search. It does not explicitly name a sibling tool it is distinct from, keeping it out of 5 territory.

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 leading phrase list ('What's new with X', 'latest on Y', 'what happened to Z this week/month/quarter') effectively signals the user intents this tool serves. However, there is no explicit when-not guidance and no named alternative for point-in-time facts (e.g., company_facts) or deeper research (deep_research), leaving routing to 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.