Skip to main content
Glama

Cite payments rulebook clause

cite_rulebook
Read-onlyIdempotent

Retrieve a curated payments-rulebook citation for a specific clause, with summary and source URL.

Instructions

Return a curated payments-rulebook citation for a single clause.

Use this to quote one specific rule (with its canonical source URL) once
you know the ``scheme``/``version``/``clause``. To discover which clauses
exist first, call ``list_rulebook_clauses``.

Looks up one well-known rule across the SEPA, CBPR+, and HVPS+
rulebooks and returns a short summary together with the canonical
source URL so an agent can quote the rule and the operator can
verify it against the official document.

The registry is a curated convenience layer, not a verbatim
reproduction of copyrighted text. Always defer to ``source_url``
for authoritative wording before relying on a citation for
compliance or contractual decisions; the returned ``disclaimer``
field repeats this for the calling agent.

Args:
    scheme: One of ``"SEPA"``, ``"CBPR+"``, or ``"HVPS+"`` (case
        sensitive).
    version: The rulebook version (e.g. ``"2025"`` or ``"2026"``).
    clause: A kebab-case clause identifier from
        ``list_rulebook_clauses``.

Returns:
    A citation dict ``{"scheme", "version", "clause", "title",
    "summary", "source_url", "as_of", "disclaimer"}`` or an
    ``{"error": ...}`` payload if the citation is not in the
    registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clauseYesA kebab-case clause identifier (e.g. 'iban-only') as returned by list_rulebook_clauses for the chosen scheme and version.
schemeYesThe rulebook scheme to cite: one of 'SEPA', 'CBPR+', or 'HVPS+' (case-sensitive).
versionYesThe rulebook version, e.g. '2025' or '2026'. Use list_rulebook_clauses to see which versions exist per scheme.
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds important context: the citation is a curated convenience layer (not verbatim), the need to defer to source_url for authoritative wording, and the presence of a disclaimer field.

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 well-structured with a clear first line summarizing purpose, followed by usage guidance, and then detailed arg descriptions. Every sentence adds value, and there is no repetition or fluff.

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 the simple parameters and no output schema, the description covers all necessary aspects: purpose, prerequisites, limitations, return structure, and safety notes. It is self-contained and fully explains the tool's behavior.

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?

Schema coverage is 100% with meaningful descriptions. The description adds examples (e.g., '2025', 'iban-only'), notes case sensitivity for scheme, and clarifies the dependency on list_rulebook_clauses for clause values.

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 states 'Return a curated payments-rulebook citation for a single clause,' using a specific verb and resource. It distinguishes this tool from sibling 'list_rulebook_clauses' by emphasizing that it is used once the scheme/version/clause are known.

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?

The description explicitly says to use this tool when quoting a specific rule and to first call 'list_rulebook_clauses' to discover clauses. It also mentions the supported schemes (SEPA, CBPR+, HVPS+).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/camt053-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server