Skip to main content
Glama

fi_company

Retrieve Finnish company register details by Business ID or name, including registration date, legal form, status, address, website, EUID, and VAT number, via a paid x402 call.

Instructions

Finnish company register (PRH / YTJ open data) by Business ID (Y-tunnus) or name: current name, registration date, legal form, status, trade-register status, main business line, address, website, EUID and derived VAT number. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fi_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo1-20
nameNoName search
business_idNoY-tunnus 1234567-8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the x402 price (0.002 USDC on Base), that billing is per successful call, and that an unauthenticated call returns a 402 challenge. It omits rate limits, pagination/return cardinality for name searches, and whether partial matches occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the identity of the resource, then coverage fields, then the cost/precondition sentence. The field list is dense but each item tells the agent what it can expect back; nothing is gratuitous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema or annotations, the description supplies return fields, pricing, and auth failure behavior, which covers most of what an agent needs. The main gap is the shape ambiguity between ID lookup (single record) and name search (apparently a bounded list via max), which is not resolved.

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 description coverage is 100% and already documents all three parameters (max as 1-20, name, Y-tunnus format). The description adds no format or behavior detail beyond repeating the two lookup keys, so the baseline of 3 applies.

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?

States a specific resource and scope: the Finnish company register (PRH/YTJ) keyed by Business ID (Y-tunnus) or name, and enumerates the returned fields. The country/registry qualifier immediately separates it from fr_company, no_company and uk_company, so an agent can pick it without opening the schema.

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?

Makes the two lookup modes explicit (Y-tunnus or name) and states the payment precondition, including what happens without a key. It does not say when to prefer name search over ID lookup or when not to use this tool, so a small inference remains.

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