Skip to main content
Glama
Sign In

DAP Bellwether

by solutions.dap
OverviewDiscussionsAdmin

Search regulatory changes

search_regulatory_changes
Read-only

Use when you need what financial regulators in Canada, the US, the UK or the EU have published on a topic or in a date range. Returns matching records newest first, each with its link and id. Free for 50 calls per caller each UTC day, then $0.01 USDC on Base per call via x402.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records to return, most recent first.
queryNoKeywords matched against title and summary, for example "liquidity" or "crypto-asset". Leave out to filter by the other fields alone.
sinceNoISO 8601 date or timestamp, compared in UTC. Only items published on or after this. A year, month or date alone starts at the beginning of that period; a time without a zone is UTC.
untilNoISO 8601 date or timestamp, compared in UTC. Only items published on or before this. A year, month or date alone runs to the end of that period; a time without a zone is UTC.
categoryNoRestrict to a publication type.
regulatorNoRestrict to one regulator by short name, for example OSFI, SEC, FCA, ESMA.
jurisdictionNoRestrict to one jurisdiction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum records to return."New value: +"Maximum records to return, most recent first."
    • changedInput schema / properties / query / description
      Previous value: -"Keywords matched against title and summary, for example \"liquidity\" or \"crypto-asset\"."New value: +"Keywords matched against title and summary, for example \"liquidity\" or \"crypto-asset\". Leave out to filter by the other fields alone."
    • changedInput schema / properties / since / description
      Previous value: -"ISO 8601 date or timestamp. Only items published on or after this."New value: +"ISO 8601 date or timestamp, compared in UTC. Only items published on or after this. A year, month or date alone starts at the beginning of that period; a time without a zone is UTC."
    • changedInput schema / properties / until / description
      Previous value: -"ISO 8601 date or timestamp. Only items published on or before this."New value: +"ISO 8601 date or timestamp, compared in UTC. Only items published on or before this. A year, month or date alone runs to the end of that period; a time without a zone is UTC."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value beyond that with the sort order, the fields returned for each record, and an explicit cost model (50 free calls per caller per UTC day, then $0.01 USDC on Base via x402), which is exactly the kind of operational context an agent must know before calling.

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?

Three sentences, front-loaded with the use condition, then result shape, then pricing. Every sentence carries distinct operational information and there is no filler or repetition of the name.

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?

With no output schema, the description does its duty by stating that records come back newest first with a link and an id. Coverage, filters, and limits are fully handled by the schema, and cost is disclosed, leaving only minor gaps such as total-result or pagination behavior.

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% and each parameter already documents its matching and date-normalization semantics in detail. The description only echoes 'on a topic or in a date range', adding no syntax, default, or interaction detail beyond the schema; 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 names a specific action and resource: searching publications from financial regulators in Canada, the US, the UK and the EU by topic or date range. It is clearly a search/list tool, but it never names or contrasts the siblings get_regulatory_change and recent_regulatory_changes, so an agent must infer the boundary itself.

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 you need what financial regulators ... have published on a topic or in a date range" gives a concrete triggering condition, including the two primary filter modes. There are no when-not conditions or named alternatives for the very similar recent_regulatory_changes and get_regulatory_change tools.

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