Skip to main content
Glama

BaFin supervisory measures (RSS)

get_bafin_measures
Read-only

Free. Official supervisory measures published by BaFin (German financial regulator), last 20 feed entries: date, title (unchanged, German), sector derived from the link path (insurance, banking_aml, securities_disclosure, other), url, source. Measures against natural persons are withheld. Not a rating of any company and not advice. Returns unavailable instead of estimating when the feed cannot be read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the weight, and it does add real behavior: titles are returned unchanged in German, sector is derived from the link path, and measures against natural persons are deliberately withheld. It also states failure behavior — 'returns unavailable instead of estimating' — which is valuable for an agent deciding whether to trust a result. It stops short of saying how current the feed is or how often it refreshes.

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?

Front-loaded with the cost/availability note ('Free.') and then the resource, followed by scope, field list, and caveats — a sensible information order. It is a single dense block that reads slightly as a run-on, but every clause (sector derivation, natural-person withholding, non-advice disclaimer, failure mode) carries distinct information rather than padding.

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 the necessary work by enumerating returned fields, bounding the entry count, and disclosing the non-estimation failure path, so an agent knows what a successful and unsuccessful call yield. Minor gaps remain around recency/latency of the feed and whether sector other is a catch-all, but nothing blocking is missing.

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?

There are zero parameters, so there is no per-parameter meaning to convey and the baseline is 4. The description correctly spends no words on arguments and instead describes the shape of the result, which is the only semantic information that matters for a no-arg tool.

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 names a specific source and resource — official BaFin supervisory measures from the RSS feed — and bounds the scope precisely to the last 20 entries with an explicit field list (date, title, sector, url, source). An agent can tell exactly what this returns without inspecting anything else, and the domain is clearly distinct from the unrelated data-feed siblings.

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?

Usage is only implied: zero parameters means there is nothing to configure, and the 'last 20 entries' framing signals this is a snapshot call with no paging. However, the description never states when an agent should reach for this versus another source, nor any exclusions or freshness expectations that would guide a decision.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.