DAP Bellwether
Server Details
Free regulatory change feed for financial regulators in Canada, the US, the UK and the EU.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- bsibeth234/dap-bellwether
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolsget_regulatory_changeGet a regulatory change with its revision historyRead-onlyInspect
Retrieve one record in full, including every revision observed since it was first seen. Use this to answer whether a document was amended after publication and what moved. The id comes from a search or recent result.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Record id from a search or recent result. |
list_coverageList regulators and coverage statusRead-onlyInspect
List every regulator and feed being monitored, with when each was last collected successfully and how fresh the data is. Use to answer what this connector covers, or to check whether a jurisdiction is being watched before relying on an absence of results.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
recent_regulatory_changesRecent regulatory changesARead-onlyInspect
List the most recent regulatory publications across all covered regulators, newest first. Use when asked what is new, what happened this week, or for a general catch up rather than a specific topic.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back this many days. | |
| limit | No | Maximum records to return. | |
| jurisdiction | No | Restrict to one jurisdiction. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so description doesn't need to cover safety. It adds minor context like 'newest first' ordering and scope ('all covered regulators'), but lacks details on pagination or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with action and context, no wasted words. Efficiently conveys purpose and usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with optional parameters and no output schema, the description covers purpose, usage, ordering, and scope. Minor gap: no mention of pagination but tool is low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with clear parameter descriptions. The description does not add additional meaning beyond schema for parameters like days, limit, or jurisdiction.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'most recent regulatory publications' sorted 'newest first'. It distinguishes from siblings by explicitly contrasting with 'specific topic' searches, which aligns with sibling tool search_regulatory_changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises when to use (e.g., 'what is new', 'general catch up') and when not ('rather than a specific topic'), effectively differentiating from search_regulatory_changes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_regulatory_changesSearch regulatory changesRead-onlyInspect
Search regulatory publications collected from financial regulators in Canada, the United States, the United Kingdom and the European Union. Use for questions about what a regulator has published on a topic, or what has changed in a date range. Returns the most recent matches first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum records to return. | |
| query | No | Keywords matched against title and summary, for example "liquidity" or "crypto-asset". | |
| since | No | ISO 8601 date or timestamp. Only items published on or after this. | |
| until | No | ISO 8601 date or timestamp. Only items published on or before this. | |
| category | No | Restrict to a publication type. | |
| regulator | No | Restrict to one regulator by short name, for example OSFI, SEC, FCA, ESMA. | |
| jurisdiction | No | Restrict to one jurisdiction. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!