Skip to main content
Glama

Recent Changes

recent_changes
Read-onlyIdempotent

"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 accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

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": "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. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"Window start — ISO date (\"2026-04-01\") or relative (\"7d\", \"30d\", \"3m\", \"1y\"). Use \"30d\" or \"1m\" for typical monitoring."New value: +"Window start, ISO date (\"2026-04-01\") or relative (\"7d\", \"30d\", \"3m\", \"1y\"). Use \"30d\" or \"1m\" for typical monitoring."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "since": "30d",
      +    "type": "company",
      +    "value": "AAPL"
      +  }
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses parallel fan-out across three sources, the GDELT -> GNews fallback and why it triggers (rate limits, 5xx), and that USPTO soft-fails because PatentsView was sunset. Annotations already cover readOnly/openWorld/idempotent, so this extra context is a genuine bonus, though latency or partial-result behavior of the parallel fan-out is not spelled 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?

Front-loaded with intent-matching phrases that earn their place for retrieval, and the source/fallback detail is useful. The opening sentence is long and runs several clauses together plus a literal quoted `since`, which slightly blurs the structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no output schema, the description supplies the missing return contract (changes[] grouped by source, total_changes, pipeworx:// citation URIs) plus degradation behavior per source. Nothing needed to call or interpret the result is absent.

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 coverage is 100% and the schema already documents `since` formats, `value` as ticker/CIK, and the `type` enum, so the description mostly restates those. The worked examples in the description reinforce but do not extend the schema's meaning; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and operation: a change feed for a company over a window, fanned out to named sources (SEC EDGAR, GDELT/GNews, USPTO). It explicitly distinguishes itself from the sibling entity_profile by contrasting windowed changes vs. static profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives concrete trigger phrasings ("what's new with X", "latest on Y", "what happened to Z this week") that map natural user intent to this tool, and names the alternative with the exact condition that selects it: use entity_profile when the static profile is wanted regardless of window.

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.