Skip to main content
Glama

Cite payments rulebook clause

cite_rulebook
Read-onlyIdempotent

Retrieve a curated citation from SEPA, CBPR+, or HVPS+ rulebooks for a specific clause, including summary and canonical source URL. Use after discovering clauses via list_rulebook_clauses.

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 payments-rulebook scheme to cite (case-sensitive). Must be exactly one of: 'CBPR+', 'HVPS+', 'SEPA' (see list_rulebook_clauses).
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, idempotentHint, and destructiveHint as safe. The description adds crucial behavioral context: the registry is a curated convenience layer, not a verbatim reproduction; always defer to source_url; the disclaimer field repeats this. This goes beyond annotations to explain limitations and usage boundaries.

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-organized into paragraphs with clear sections. It is concise (about 150 words) with no redundant sentences. Every sentence adds value: purpose, usage context, parameter guidance, and caveats. Front-loaded with the core action.

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 3 required params with full schema coverage, annotations, and no output schema, the description compensates by explicitly listing the return dict fields ('a citation dict {scheme, version, clause, title, summary, source_url, as_of, disclaimer}'). This gives the agent a complete picture of what to expect.

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%, so the baseline is 3. The description adds value by clarifying case sensitivity for 'scheme', giving examples for 'version', and explaining that 'clause' should be a kebab-case identifier from list_rulebook_clauses. It connects parameters to the sibling tool, making the API more intuitive.

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 starts with a clear verb+resource: 'Return a curated payments-rulebook citation for a single clause.' It distinguishes itself from the sibling tool 'list_rulebook_clauses' by instructing the agent to use that first to discover clauses, showing a specific usage path.

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 states when to use this tool ('once you know the scheme/version/clause') and when not to ('To discover which clauses exist first, call list_rulebook_clauses'). It also provides guidance on deferring to the source URL for authoritative wording, which is critical for compliance.

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