German BNetzA SMARD & § 14a EnWG Grid Fee Preview Oracle

screen_sanctions_and_kyb

Deterministic EU FSF, UN & OpenSanctions KYB screening issuing signed Ed25519 Non-Hit VCs.

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": {
      "entity_name": "<entity_name>"
    },
    "name": "screen_sanctions_and_kyb"
  }
}

Input Schema

Name	Required	Description	Default
`entity_name`	Yes	Legal company or beneficiary name to screen.
`country_code`	No	ISO-3166-1 alpha-2 country code.	DE
`vat_or_lei_id`	No	Optional EU VAT ID or LEI identifier.
`max_accepted_fee_eur`	No	Maximum fee in EUR your agent is willing to pay per call (list price 0.02 EUR). Omit if not willing to pay.
`ap2_intent_mandate_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: the result is deterministic and it emits signed Ed25519 credentials, and the 'Non-Hit' qualifier implies hits are handled differently. It nevertheless omits major behavior: what happens on a hit, authentication requirements, external API dependency/latency, and that the call is paid (the fee only appears in the schema).

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?

It is a single front-loaded sentence with no filler. Its density is efficient but borders on cryptic, since four acronyms carry the whole semantic load.

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

Completeness3/5

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

For a 5-parameter, paid, externally dependent screening tool with no annotations and no output schema, the description is only partially complete. It should explain what a Non-Hit VC contains and how a hit or payment refusal surfaces, given there is no output schema to fall back on.

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 description coverage is 80%, so most parameters are already documented in the schema and baseline 3 applies. The description adds no per-parameter meaning, and the one undocumented parameter (ap2_intent_mandate_id) is left unexplained in both places.

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 operation (KYB screening) and specific sources (EU FSF, UN, OpenSanctions), plus the artifact produced (signed Ed25519 Non-Hit VCs). It is distinguishable from the siblings (PII redaction, e-invoice validation) by domain, though the heavy acronym load (KYB, VC, FSF) makes the exact purpose harder to parse than it needs to be.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives or when to prefer the sibling tools. The only implicit signal is that this is a compliance-screening step, which the agent must infer.

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

All German BNetzA SMARD & § 14a EnWG Grid Fee Preview Oracle 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?