Skip to main content
Glama

eurc402 — EU compliance (VAT + company data)

by com.eurc402

Look up an EU company (paid full record)

lookup_eu_company

Detect the jurisdiction of a company registration number for FREE across 10 EU registers (no, fr, fi, sk, gb, lv, ro, ee, cz, pl). The FULL normalized record (legal name, status, legal form, registered address, incorporation date, officers, provenance) is a PAID x402 service (EUR 0.05/call in EURC or USDC on Base) — this tool returns the exact paid endpoint, price, and how to pay.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCompany/registration number: SIREN (FR), org.nr (NO), Y-tunnus (FI), IČO (SK), company number (UK), regcode (LV), CUI or J-number (RO).
countryNoOptional ISO country code to disambiguate; otherwise auto-detected from the id.

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description partially covers behavior: it notes the free detection and paid endpoint info. But it does not mention error handling, rate limits, or what happens on invalid IDs.

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?

The description is a single sentence, fairly concise. It front-loads the key benefit (free detection) but could be structured more cleanly with bullet points or shorter clauses.

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

Completeness3/5

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

The description omits details on the free detection output format and error states. Given no output schema, more completeness would be beneficial for an agent to correctly invoke and interpret the tool.

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% and contains detailed parameter descriptions. The tool description does not add further parameter semantics beyond what the schema already provides, meeting the baseline.

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 the tool detects jurisdiction for free and provides info on the paid full record. It distinguishes itself from siblings by focusing on company lookup vs list or VAT validation.

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?

The description explains the free detection and paid record option, giving context on when to use. However, it does not explicitly contrast with siblings or state prerequisites.

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

All eurc402 — EU compliance (VAT + company data) toolsInspect
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.2/5.0
Disambiguation5/5

Each tool has a distinct purpose: listing supported countries, looking up a company (with a free jurisdiction detection and a paid full record), and validating EU VAT numbers. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: list_supported_countries, lookup_eu_company, validate_eu_vat. Easy to predict and read.

Tool Count5/5

Three tools is appropriate for the domain of EU compliance covering VAT validation and company data lookup. Neither too few nor too many.

Completeness4/5

The set covers key operations: discovering coverage, detecting jurisdiction, and validating VAT. A minor gap is the lack of a tool to directly handle the paid service, but the descriptions guide the user externally.

Resources