Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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

B3.4/5.0
Behavior3/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 disclose genuinely useful behavior: parallel fan-out across three sources, GDELT preferred with GNews fallback under rate limiting or 5xx, and USPTO soft-failing after the PatentsView sunset. It does not explain what the merged response looks like, how partial failures are surfaced, or any auth/rate-limit constraints on the caller side.

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 opening is front-loaded with a dense list of user phrasings before stating the actual function, and the whole thing is a single run-on sentence. More importantly, it terminates mid-sentence ("`since` acc..."), which is a structural defect rather than mere brevity.

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-required-parameter aggregation tool with no annotations and no output schema, the description covers sources and window semantics competently, but the truncated ending leaves the `since` guidance unfinished and says nothing about the merged result shape or how per-source failures appear to the caller.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters including the accepted relative and ISO formats for `since`. The description reinforces the window semantics in prose ("last N days/weeks/months") but the sentence trailing `since` is cut off mid-word, adding no new format detail beyond the schema.

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 names a specific resource (a consolidated change feed for a company over the last N days/weeks/months) and enumerates the underlying sources (SEC EDGAR filings, GDELT/GNews news, USPTO patents), so the operation is unmistakable. It does not explicitly distinguish itself from sibling tools such as company_facts or entity_profile, which keeps it short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The quoted example phrasings ("what's new with X", "latest on Y", "news on Tesla recently") give an agent useful routing cues for when this tool applies. However, there is no explicit when-not condition and no named alternative for adjacent needs like static company facts or alert subscriptions.

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.