Velvoite — EU Financial Regulatory Compliance

get_obligations

Read-only

Get regulatory obligations - specific requirements extracted from regulations.

Each obligation includes the requirement text, applicable article reference,
deadline, which entity types it applies to, actor roles, and current status.
Results are paginated (max 50 per page).

Supports keyword search via the query parameter (trigram + ILIKE matching on obligation text).
Combine with regulation, entity_type, and actor_role filters for precise results.

Set canonical=True to get deduplicated canonical obligations with enforcement
intelligence instead. Canonical obligations return one entry per unique legal
requirement per actor role, with compliance difficulty and enforcement metrics.

Use get_actor_roles first to discover available actor roles per regulation.

Args:
    entity_type: Filter by entity type code (e.g. 'credit_institution', 'payment_institution').
    regulation: Filter by regulation code (e.g. 'dora', 'mica', 'aml').
    status: Filter by status: 'upcoming', 'active', 'overdue', or 'expired'.
    query: Keyword search on obligation text (e.g. 'ICT risk', 'strong customer authentication').
    actor_role: Comma-separated actor roles to filter by (e.g. 'credit_institution,significant_institution'). Use get_actor_roles to see available roles.
    canonical: If True, return deduplicated canonical obligations with enforcement intelligence instead of raw obligations.
    page: Page number (default 1).
    per_page: Results per page (default 20, max 50).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`query`	No
`status`	No
`per_page`	No
`canonical`	No
`actor_role`	No
`regulation`	No
`entity_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

The description adds significant behavioral context beyond the readOnlyHint annotation: pagination limits, trigram + ILIKE search, canonical mode semantics, and the structure of returned obligations. It provides rich detail about how the tool behaves, far exceeding what annotations alone convey.

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 summary, usage notes, and a detailed Args list. Each sentence provides essential information without redundant padding. The length is justified by the complexity of the tool, and the organization improves readability.

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?

The description covers the tool's purpose, key behaviors, all parameters, pagination, search, and canonical mode. With an output schema present, describing return values is unnecessary. For an 8-parameter tool, this description is complete and self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the schema having no per-parameter descriptions (0% coverage), the description's Args section thoroughly explains every parameter, including valid examples, value ranges, and cross-references (e.g., actor_role uses get_actor_roles). This fully compensates for the schema's lack of detail.

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 it retrieves regulatory obligations, with a specific verb ('Get') and resource ('regulatory obligations'). It distinguishes itself from siblings by explaining the difference between raw obligations and canonical obligations via the canonical flag. The phrase 'specific requirements extracted from regulations' adds precision.

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

Usage Guidelines4/5

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

Provides clear guidance on when to use the tool, including combining filters and using get_actor_roles first. However, it does not explicitly mention alternatives (e.g., get_canonical_obligations) or when not to use this tool, so it falls short of a 5.

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

All Velvoite — EU Financial Regulatory Compliance tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Each tool targets a distinct resource (obligations, documents, enforcement, Finnish statutes, CJEU cases) with clear parameter differences. Minor overlap exists between get_obligations and get_canonical_obligations, but descriptions explicitly differentiate them.

Naming Consistency5/5

All tools consistently use verb_noun patterns: get_ for retrievals, search_ for queries, list_documents, and audit_taxonomy. No mixed casing or inconsistent verb styles are present.

Tool Count2/5

At 26 tools, the surface exceeds the 25-tool threshold for 'too many'. While the domain is broad, the large number of specialized search/get tools could be consolidated without losing functionality.

Completeness4/5

The API covers the full regulatory compliance workflow: company profile, obligations, deadlines, documents, enforcement, and multiple legal sources (EU, Finnish, CJEU). Some Finnish/KHO tools return URLs requiring web fetch rather than direct data, which is a minor but by-design gap.

Resources

Need Help?