Skip to main content
Glama
Sign In

DAP Bellwether

by solutions.dap
OverviewDiscussionsAdmin

Get a regulatory change with its revision history

get_regulatory_change
Read-only

Use when you have a record id and need to know whether the publication was amended and what changed. Returns the record in full with every revision observed since first collection. Free for 50 calls per caller each UTC day, then $0.01 USDC on Base per call via x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesRecord id from a search or recent result, 32 lower case hexadecimal characters. The answer shows each revision oldest first, so an amendment after publication and what moved are both visible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Record id from a search or recent result."New value: +"Record id from a search or recent result, 32 lower case hexadecimal characters. The answer shows each revision oldest first, so an amendment after publication and what moved are both visible."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description provides highly valuable operational data that is not in the annotations, including the tiered pricing structure, call limits (50 calls), and associated crypto transaction details (USDC on Base).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, efficiently combining the tool's core function with critical operational metadata (cost/rate limits) in a well-structured paragraph.

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 its low complexity (1 parameter) and the presence of annotations, the definition is complete, covering the precise use case, limitations, and external operational constraints.

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?

While the schema is highly descriptive, the description reinforces the semantic meaning of the ID—that it is a specific 'record id' used to retrieve historical amendments rather than just a random identifier. This adds useful intent to the parameter usage.

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 specifies the operation (get a record) and its function (review amendments and changes), providing context that distinguishes it from broader search or listing tools among the siblings.

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?

It provides a direct usage guideline: 'Use when you have a record id,' implicitly directing users away from the sibling tools that require broader search criteria or list generation.

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

All DAP Bellwether 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