Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.7/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 largely does so: it discloses the three upstream sources, the parallel fan-out, the preferred/fallback news provider with the specific failure conditions (rate limit, 5xx), and that USPTO will soft-fail because PatentsView was sunset in May 2025. It stops short of saying whether partial results are returned or errors are surfaced per-source, and never describes response shape.

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 stack of five quoted example queries is redundant with each other and front-loads noise before the actual capability statement. The technical detail that follows is dense and useful, but the definition is visibly cut off at the end, so it neither reads as complete nor as well-shaped.

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 multi-source fan-out tool with no output schema and no annotations, source-level behavior is covered well, but the reader still cannot tell what the returned payload looks like (per-source sections? merged items?) and the description is truncated. Adequate but with a real gap for an aggregator of this complexity.

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 defines type, since and value with format examples. The description only echoes the since window framing and the company-only entity scope, and its one attempt to elaborate on `since` is truncated. Baseline 3 is appropriate.

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 concrete verb and scope: a change feed for a company over the last N days/weeks/months, executed as one parallel call fanning out to SEC EDGAR, GDELT/GNews and USPTO. The core is unambiguous, but the actual purpose statement is buried behind five quoted user phrasings and the description cuts off mid-sentence ('`since` acc'), leaving the closing thought 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?

The quoted trigger phrasings ("what's new with X", "latest on Y", "updates on Acme") map user intent to this tool clearly, and the GDELT-preferred / GNews-on-rate-limit-or-5xx rule gives operational guidance. It never states when NOT to use it or names any alternative tool for narrower news-only or filing-only needs.

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.