tollbooth

regulatory_pulse

Regulatory pulse — SEC Atom RSS + openFDA adverse + USPTO TSDR + FCC OET + FAA registry hints for bio/tech Polymarkets. Returns events by org + provenance.

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

Input Schema

Name	Required	Description	Default
`org`	No	all\|sec\|fda\|uspto\|fcc\|faa\|openfda
`hours_back`	No	Hours back, default 24

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations are empty, so description carries the burden. It lists data sources but doesn't disclose read-only nature, side effects, or rate limits. Adequate but not comprehensive.

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?

Two sentences convey purpose and sources efficiently. Front-loaded with key details. Slightly dense but concise overall.

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

Completeness2/5

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

No output schema; description only vaguely states 'returns events by org + provenance'. Missing return structure, event format, and 'hints' explanation. Incomplete for a multi-source aggregator.

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%, so baseline is 3. Description mentions 'by org' but does not add meaningful detail beyond schema descriptions. No improvement over structured data.

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?

Description clearly states tool aggregates regulatory signals from multiple agencies (SEC, FDA, USPTO, FCC, FAA) and returns events by org and provenance. This differentiates it from sibling tools that focus on single sources.

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?

No explicit when-to-use or alternative mentions. The list of sources implies usage for multi-agency regulatory pulse, but an agent could benefit from guidance to use specific sibling tools for single-source queries.

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

All tollbooth tools Inspect

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

Need Help?