Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.9/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 burden and does well: it discloses the per-source fallback chain (GDELT preferred, GNews on rate-limit/5xx), that USPTO soft-fails because PatentsView was sunset in May 2025, and that EDGAR filtering is by `since`. It does not describe the merged response shape, partial-source failure reporting, or empty-result behavior.

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?

Query phrasings are front-loaded so an agent can pattern-match user intent before reading the mechanics, and the source/fallback detail follows in a compact run-on. The only structural defect is the truncated tail, which is a data quality issue rather than wasted wording.

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 three-source aggregation tool with no output schema, the description covers sources and failure modes but not the returned payload — whether results are per-source buckets, a merged timeline, or how counts are reported. The truncation at '`since` acc' removes what appears to be guidance about accepted window values, leaving a genuine hole for a tool with no annotations to fall back on.

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 `type`, `value`, and `since` are already fully documented with enum, example formats, and relative-window syntax. The description adds only a marginal hint about `since` controlling the EDGAR filing window before being truncated, so the 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?

States a specific verb and resource: a change feed for a company over the last N days/weeks/months, aggregated from SEC EDGAR, GDELT/GNews, and USPTO. The multi-source fan-out clearly separates it from the numerous single-domain '*__recent_changes' siblings, though the description is cut off mid-sentence ('`since` acc'), leaving the final scoping detail unfinished.

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?

Opens with a strong set of natural-language triggers ("What's new with X", "latest on Y", "news on Tesla recently") that tell an agent exactly which user phrasing should route here. It also implies the one-call-parallel-fan-out advantage over calling sources separately, but never explicitly names an alternative tool or states when NOT to use it.

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.