Skip to main content
Glama

fi_get_act

Read-onlyIdempotent

Fetch metadata for Finnish statutes by providing the act's year and number. Access official legal data from Finlex.

Instructions

Fetch statute metadata by year and number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYese.g. ``2018``.
numberYese.g. ``1050``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
numberNo
titleNo
subtypeNo
frbr_uriNo
date_issuedNo
date_publishedNo
eli_uriNo
human_readable_citationNo
source_urlNo
Behavior3/5

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

Annotations fully cover safety (readOnly, idempotent) so description adds minimal extra context. Does not elaborate on what metadata includes or any side effects.

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?

Single sentence with no unnecessary words, clearly front-loads the purpose.

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 rich annotations and presence of output schema, the description covers all necessary information succinctly.

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

Parameters3/5

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

Schema coverage is 100% with simple parameter descriptions. Description confirms usage of year and number but adds no new semantics beyond the 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?

Clear verb 'fetch', specific resource 'statute metadata', and unique selection criteria 'by year and number'. Distinct from siblings which suggest full text or listing.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool over fi_get_text or fi_list_acts. Context can be inferred but not stated.

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/matematicsolutions/fi-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server