Velvoite — EU Financial Regulatory Compliance

get_actor_roles

Read-only

Get available actor roles per regulation with obligation counts.

Actor roles define WHO an obligation applies to within a specific regulation
(e.g. 'credit_institution', 'significant_institution' for CRD/CRR, or
'ai_provider', 'high_risk_deployer' for AI Act).

Use this to discover which roles exist before filtering obligations with
get_obligations(actor_role=...).

Returns roles grouped by regulation, sorted by obligation count.
Each role includes a human-readable label and description.

Args:
    regulation: Filter to a specific regulation code (e.g. 'dora', 'ai_act'). If omitted, returns roles for all regulations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`regulation`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A5/5.0

Behavior5/5

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

Beyond the read-only annotation, the description discloses that results are 'grouped by regulation, sorted by obligation count' and each role includes 'a human-readable label and description.' It also specifies the behavior of an omitted regulation parameter. No contradictions with annotations.

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 concise and well-structured: a one-sentence summary, a brief conceptual explanation, usage guidance, return behavior, and an Args section. Every sentence adds value, with examples aiding clarity.

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?

For a single-parameter, read-only discovery tool with an output schema present, the description covers purpose, usage, parameter semantics, and return structure. No critical gaps exist.

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?

The schema provides minimal information (anyOf string/null), but the description's Args section fully explains the 'regulation' parameter with examples and default behavior, compensating for the 0% schema description coverage.

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 opens with a specific verb-resource combo: 'Get available actor roles per regulation with obligation counts.' It further clarifies the concept with concrete examples (e.g., 'credit_institution' for CRD/CRR) and distinguishes its role as a discovery step before using get_obligations, the key sibling tool.

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 instructs to 'Use this to discover which roles exist before filtering obligations with get_obligations(actor_role=...)', naming the alternative and giving a clear usage scenario. This provides both a positive use case and an implicit exclusion (not for filtering itself).

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?