Skip to main content
Glama

List rulebook clauses

list_rulebook_clauses
Read-onlyIdempotent

Browse the citation registry to find rulebook clause IDs. Filter by scheme (e.g., SEPA) and version (e.g., 2026) to narrow results.

Instructions

List the curated rulebook clauses the server can cite, optionally filtered.

Use this to browse the citation registry and pick a ``clause`` id; then pass
that id to ``cite_rulebook`` to fetch the full summary and source URL.

Returns the full registry, optionally filtered by ``scheme`` and /
or ``version``. Use the resulting ``clause`` values as input to
``cite_rulebook``.

Args:
    scheme: Restrict to one scheme (e.g. ``"SEPA"``). ``None``
        returns all schemes.
    version: Restrict to one version (e.g. ``"2026"``). ``None``
        returns all versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemeNoRestrict the listing to one scheme ('SEPA', 'CBPR+', or 'HVPS+'). None (the default) returns clauses for all schemes.
versionNoRestrict the listing to one rulebook version, e.g. '2026'. None (the default) returns clauses for all versions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds information about returning full registry with optional filtering by scheme/version, which is consistent and useful.

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?

Description is well-structured: purpose first, then usage guidance, then parameter details. Every sentence contributes meaningfully without redundancy.

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 tool's simplicity, annotations, and output schema existence, the description covers the workflow (browse to cite), filtering, and return type completely.

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 baseline is 3. Description adds examples ('SEPA', '2026') and clarifies that None returns all, which enhances clarity beyond schema.

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?

Description clearly states 'List the curated rulebook clauses' and distinguishes from sibling 'cite_rulebook' by specifying this tool is for browsing to get clause IDs. Verb and resource are specific.

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?

Explicitly says 'Use this to browse the citation registry and pick a clause id; then pass that id to cite_rulebook'. Provides when-to-use and next-step guidance.

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