Skip to main content
Glama

Sec Regulations

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sec Regulations Search

sec_regulations_search
Read-onlyIdempotent

Keyword search across the SEC regulations — US securities regulation in 17 CFR (SEC and CFTC). Answers "what SEC regulations cover X", "the SEC rule about X", "find the securities regulation for X", "which disclosure requirement applies to X", "the CFTC regulation on X". Great for topics: insider trading and material nonpublic information, disclosure requirements and MD&A, registration statements and exempt offerings, private placements and accredited investors, proxy solicitations and shareholder proposals, broker-dealer net capital and customer protection, investment adviser fiduciary duty and custody, market structure and short sales, tender offers, beneficial ownership reporting, swaps and commodity futures. Returns matching securities rules with citation (17 CFR), heading, excerpt, and source URL. Example: sec_regulations_search({ query: "insider trading" }); sec_regulations_search({ query: "accredited investor definition", limit: 15 }). Keyless. Searches the SEC RULES text; the separate edgar and sec-xbrl packs search SEC filings data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return, 1-20 (default 10).
queryYesSecurities-regulation topic or phrase, e.g. "insider trading", "accredited investor definition", "management discussion and analysis", "net capital requirements", "short sale".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "insider trading"
+  },
+  {
+    "limit": 15,
+    "query": "accredited investor definition"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that it is keyless, searches SEC rules text, and returns citations, headings, excerpts, and source URLs. No contradictions.

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?

Well-structured with purpose first, then examples, then return info. Slightly long due to topic list but no wasted sentences. Could be trimmed slightly but still effective.

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?

Given no output schema, description adequately explains return values (citation, heading, excerpt, source URL). Examples further clarify usage. Complete for a search tool with full schema coverage.

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 covers both parameters at 100%. Description reinforces with examples (e.g., 'insider trading') and clarifies limit range (1-20, default 10). Adds value over schema by showing usage patterns.

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?

The description clearly states the tool does keyword search across SEC regulations in 17 CFR, with specific examples of queries and topics. It distinguishes from siblings like edgar and sec-xbrl by stating it searches rules text, not filings.

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?

Provides example queries and topic areas where the tool is great, and notes that separate packs search filings data. However, it does not explicitly differentiate from the sibling tool `sec_regulation` or state when not to use it.

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

All Sec Regulations 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