Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.8/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 behavioral burden and does substantial work: it discloses the fan-out to three sources, the GDELT->GNews fallback order including rate-limit/5xx conditions, and a known soft-failure (USPTO/PatentsView sunset May 2025). What it does not disclose is the response shape or what happens when every source fails, and the trailing "`since` acc" sentence is cut off mid-word.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent examples are front-loaded and help routing, but six quoted phrasings is more than needed for the same signal. More seriously, the final sentence terminates mid-word ("`since` acc"), which is a structural defect that truncates whatever caveat was intended.

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 multi-source aggregation tool with no output schema, the description gives an agent enough to call it correctly and to interpret partial results, since source coverage and degradation behavior are spelled out. The only meaningful gap is the truncated closing sentence and the absence of any statement about what a merged response looks like.

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 the schema already documents `type`, `value`, and `since` (including relative formats like "30d" and the "30d"/"1m" recommendation). The description reinforces that the window drives source coverage ("filings since `since`") but its one parameter-focused sentence is truncated at "`since` acc", adding no usable detail beyond the schema. 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?

The definition states a specific resource and scope: a "change feed for a company in the last N days/weeks/months in ONE parallel call," and enumerates the three upstream sources (SEC EDGAR, GDELT/GNews, USPTO). An agent can tell exactly what this returns without opening the schema. It never names a sibling tool or draws a boundary against them, which keeps it from a 5.

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?

The leading quoted intents ("what's new with X", "latest on Y", "what happened to Z this week") give clear triggers for when to reach for this tool, and "ONE parallel call" implicitly steers the agent away from calling each source separately. There is no explicit when-not guidance or named alternative for adjacent needs such as entity profiles or alerts.

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.