Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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 real work: it discloses that the call fans out in parallel to SEC EDGAR, GDELT and USPTO, that news uses GDELT with a GNews fallback when rate-limited or on 5xx, and that the USPTO leg soft-fails due to the PatentsView sunset. That degradation/partial-failure information is exactly the kind of behavior an agent needs. It does not describe the response shape, whether partial results are still returned, or latency implications of the parallel fan-out.

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 definition is front-loaded with trigger phrasings before the technical fan-out detail, which is the right ordering for tool selection. Six quoted paraphrases are somewhat repetitive, and the final sentence trailing off at "`since` acc" leaves an unfinished clause that adds noise rather than value.

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 three-parameter aggregation tool with no output schema, the description covers what sources are hit, how fallback works, and which leg may be dead — the information an agent most needs to decide whether to call it. The truncated trailing sentence and the absence of any hint about the returned structure leave a small but real gap.

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 all three parameters (type enum, since formats, value as ticker or zero-padded CIK) are already documented in the schema. The description's reference to `since` and the window semantics adds little beyond that, and the sentence that appears to elaborate on `since` acceptance is cut off mid-word. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource and scope: a change feed for a company over the last N days/weeks/months, aggregating SEC filings, news and patents. The opening cluster of quoted user phrasings ("what's new with X", "updates on Acme") makes the intent unmistakable. It stops short of naming a sibling to route away from, which keeps it at 4 rather than 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 quoted trigger phrases ("latest on Y", "what happened to Z this week / month / quarter") effectively communicate the conditions under which an agent should pick this tool rather than a static-facts tool. What is missing is any explicit exclusion or named alternative for overlapping needs, so the agent must infer boundaries.

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.