Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

U.S. regulatory & disclosure pack: Federal Register rules/notices + latest SEC 8-K, 13F, N-PORT filings

us_regs

Use when an agent must track new U.S. rules, proposed rules, agency notices and fresh SEC disclosures. Input: optional q (topic), agency (Federal Register slug), doc_type, form (8-K, 13F-HR, NPORT-P...), source, days, limit. Output: JSON Federal Register documents (type, agencies, abstract, effective/comment dates, CFR, links) and latest SEC filings by companies/funds (form, filer, CIK, filed, link). Metadata only. Example: ?days=30&source=federal_register Price: $0.0045 USDC (Base or Solana) via x402.

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": "us_regs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoTopic keywords (Federal Register full text; filters SEC filer names). Empty lists are not an error
daysNoLook-back window in days (default 7)
formNoSEC forms, comma-separated (8-K, 13F-HR, NPORT-P, 10-K, 10-Q, 6-K, S-1, N-CSR); default 8-K,13F-HR,NPORT-P
limitNoMax items per source (default 10)
agencyNoFederal Register agency slug
sourceNoWhich source (default all)
doc_typeNoFederal Register document type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Topic keywords (Federal Register full text; filters SEC filer names)"New value: +"Topic keywords (Federal Register full text; filters SEC filer names). Empty lists are not an error"
  2. Added

TDQS

A4/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 it discloses two non-obvious traits: the paid x402 model ($0.0045 USDC on Base or Solana) and that results are 'metadata only', not full text. Defaults and an example query are also shown. It omits any statement about pagination limits, error handling, or sorting behavior.

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 description is front-loaded with the 'Use when' trigger, followed by compact Input/Output/Price blocks that are easy to scan. The example query string and price line are short, but listing all seven parameters in prose largely repeats the schema. No sentence is harmful, but a few are redundant.

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?

Because there is no output schema, the description must explain the return shape; it does so field by field for both source types (type, agencies, abstract, dates, CFR, links; form, filer, CIK, filed, link). Cost, defaults, and the metadata-only limit are covered. Pagination and error behavior remain unspecified for a seven-parameter tool.

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 baseline is 3, but the description goes further: it tells the reader which of the two sources each filter affects (q hits Federal Register full text and SEC filer names) and supplies a concrete query example with days and source. It doesn't add syntax detail for agency slugs or doc_type values. That is slightly more than the schema alone.

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 first sentence names a specific verb-resource pair: tracking new U.S. Federal Register rules/proposed rules/notices plus fresh SEC disclosures. The title's 'regulatory & disclosure pack' framing clarifies that this combines two sources, which implicitly distinguishes it from the SEC-only sibling sec_filings. It never names that sibling though, so it doesn't fully differentiate.

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?

'Use when an agent must track new U.S. rules, proposed rules, agency notices and fresh SEC disclosures' gives a clear trigger context. It offers no explicit when-not conditions and no named alternative, so an agent has to infer that sec_filings should be used for SEC-only queries. Clear context, but no exclusions.

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

All 1gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources