Skip to main content
Glama

get_recent_regulator_news

Retrieve recent press releases and news from selected US financial regulators (OCC, SEC, CFTC, Federal Reserve, Treasury, FinCEN) with source and result limits.

Instructions

Recent press releases / news items from a US financial regulator (OCC, SEC, CFTC, Federal Reserve, Treasury, FinCEN) or all of them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_regulator_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (default 15).
sourceNoRegulator to pull from. 'all' fans out in parallel.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it says nothing about result ordering, time window, whether items are deduplicated across sources, or failure behavior when one regulator's feed is unavailable. The one genuinely useful trait — that 'all' fans out in parallel — is stated in the schema parameter description, not the tool description.

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?

A single front-loaded sentence with no filler; the resource is stated before the qualifiers. It is arguably over-terse rather than padded, and the parenthetical regulator list slightly duplicates the enum.

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 simple two-optional-parameter read tool, the description covers what is returned at a high level. Without annotations or an output schema, though, it should say more about the shape of returned items and the recency window, which are the two things an agent most needs to call it correctly.

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 both parameters (limit with min/max/default, source enum with the fan-out note) are fully documented in the schema. The description only restates the regulator list already present in the enum, adding no new parameter meaning; 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?

The description states a specific verb+resource ('Recent press releases / news items') and enumerates the six covered regulators, so an agent knows exactly what corpus this returns. It does not explicitly contrast itself with the sibling search_regulator_news, leaving the recency-vs-search distinction to inference.

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?

'Recent' implies a recency-based pull rather than keyword search, which implicitly separates it from search_regulator_news. However, no explicit when-to-use/when-not guidance, no mention of prerequisites, and no statement about how far back 'recent' reaches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.