Velvoite — EU Financial Regulatory Compliance

search_kho_decisions

Read-only

Return a search query to discover KHO (Finnish Supreme Administrative Court)
precedent decisions for a given year.
Requires Velvoite Premium API key.

NOTE: The Finlex listing page is client-side rendered and cannot be fetched directly.
Use the returned search_query with web_search instead — this returns an indexed list
of decisions from kho.fi that can then be fetched individually.
Then use get_kho_decision(year, number) to retrieve a specific decision.

Args:
    year: Year to browse (e.g. '2024', '2023').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses that it returns a search query rather than decisions, requires a premium key, and cannot directly fetch the Finlex page. These are valuable behavioral details beyond the readOnlyHint and openWorldHint annotations, with no contradictions.

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, front-loaded with the core purpose, and structured with a NOTE and Args section. Each sentence adds necessary information 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 simplicity of a single parameter and the existence of an output schema, the description is complete. It covers the prerequisite, the limitation, the workflow, and the next step, making it fully contextual.

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?

The schema only labels the parameter as 'Year', while the description adds 'Year to browse (e.g. '2024', '2023')', providing context and examples. While basic, this compensates for the 0% schema description coverage adequately for a single simple parameter.

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 that the tool returns a search query to discover KHO precedent decisions for a given year. It distinguishes itself from get_kho_decision by explaining the returned query is for web_search, not direct retrieval.

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?

Provides explicit workflow: use the returned search_query with web_search, then fetch individually with get_kho_decision. Also mentions the API key requirement and explains why direct fetching is impossible (client-side rendering), giving clear when-to-use context.

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?