Skip to main content
Glama
Sign In

Fuentio: UK, France & Spain company data from official registries

by com.fuentio
OverviewDiscussionsAdmin

A company's EU VAT number (registration not checked)

check_vat
Read-onlyIdempotent

Give a company's EU VAT number and how it was obtained. Registration is never checked: the answer links the official VIES page. Use it to fill an invoice or a supplier file. Don't use it as proof of VAT registration: check it on VIES. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: number, origin (published or computed), registration_checked false, note, check_url. Limits: 1 unit. Spain: no VAT numbers published. Read-only.

Input Schema

NameRequiredDescriptionDefault
countryYesISO country code: FR or ES or GB.
identifierYesOfficial ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code: FR or ES."New value: +"ISO country code: FR or ES or GB."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "FR",
-  "ES"
-]New value: +[
+  "FR",
+  "ES",
+  "GB"
+]
    • changedInput schema / properties / identifier / description
      Previous value: -"Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266."New value: +"Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790."
    • changedInput schema / properties / identifier / examples
      Previous value: -[
-  "441639465",
-  "VI-23266"
-]New value: +[
+  "441639465",
+  "VI-23266",
+  "00445790"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations cover read-only and idempotent, but the description adds substantial behavioral context beyond them: it discloses that registration is never checked, that the answer links the official VIES page, that origin can be 'published or computed', and a note field. The 'Spain: no VAT numbers published' data-quality caveat and the '1 unit' cost are useful non-obvious context. It does not contradict the readOnly annotation.

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?

Front-loaded with purpose and non-use case, then Inputs, Returns, Limits sections. Every line earns its place with zero filler; structured labels make it scannable.

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?

Complete for a 2-param, low-complexity lookup. It covers inputs, return fields, the openWorld behavior (VIES link), data-quality limits (Spain), cost, and safety, and an output schema exists so return details needn't be exhaustive.

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?

Schema coverage is 100% and documents both parameters in detail, so baseline is 3. The description reinforces this by naming country and identifier, giving the example pair ('FR', '441639465'), and cross-referencing sibling tool lookup_company as the source of identifier semantics, which adds navigational value.

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 states a specific verb+resource (give a company's EU VAT number) and clarifies the scope (registration NOT checked, registration_checked false). It distinguishes the tool from what a naive agent would expect, explicitly routing to 'check on VIES' for proof of registration.

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?

Explicitly states when to use (filling an invoice or supplier file) and when not to use (as proof of VAT registration — check VIES). Names the alternative action directly. Nothing left to inference.

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

All Fuentio: UK, France & Spain company data from official registries toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources