Velvoite — EU Financial Regulatory Compliance

get_kho_decision

Read-only

Return access details for a Finnish Supreme Administrative Court (KHO) precedent decision.
Requires Velvoite Premium API key.

KHO decisions are cited as KHO:YYYY:N (e.g. KHO:2024:52).
Use search_kho_decisions(year) to browse all decisions for a given year.

ACCESS PATTERN — follow this order:
1. Use the returned search_query with web_search to find the kho.fi page
2. From search results, fetch the kho.fi URL directly
3. Do NOT fetch finlex_url directly — Finlex requires prior search provenance

Args:
    year: Decision year (e.g. '2024').
    number: Decision number within the year (e.g. '52').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`number`	Yes

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 readOnlyHint and openWorldHint annotations, the description adds meaningful context: requires 'Velvoite Premium API key', mandates a search-first access pattern, and warns that Finlex requires prior search provenance. It also implies a returned search_query 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 information-dense and well-structured: starts with purpose, then prerequisites, citation context, alternative, and a numbered access pattern. Every sentence contributes essential guidance, and the Args section is clearly formatted.

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 complexity (access pattern, API key requirement, citation format) and the presence of an output schema, the description covers all necessary aspects for selecting and invoking the tool correctly. It also references sibling functionality for broader browsing.

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 input schema provides no descriptions (0% coverage), but the description's Args section explains both 'year' and 'number' with format and examples ('Decision year (e.g. '2024')', 'Decision number within the year (e.g. '52')'). This fully compensates for the schema gap.

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 access details for a Finnish Supreme Administrative Court (KHO) precedent decision' with a specific verb and resource. It also differentiates from sibling search_kho_decisions by explicitly noting that tool for browsing all decisions.

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?

It directly references an alternative ('Use search_kho_decisions(year) to browse all decisions for a given year') and provides a detailed access pattern with ordering and an explicit prohibition ('Do NOT fetch finlex_url directly'). This gives clear when-to-use and how-to-use guidance.

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?