Skip to main content
Glama
Sign In

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

by com.fuentio
OverviewDiscussionsAdmin

Validate a company's registered address

check_address
Read-onlyIdempotent

Validate a company's registered address against the official address base: France via API Adresse (Base Adresse Nationale, IGN). Use it to check that an address exists and is the company's, or to geolocate it. Don't use it to find companies: call search_companies. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: validated (true, false or null with a reason), normalized address, BAN ids, coordinates, precision, confidence, and how many active companies share the address. Limits: 1 unit. Spain not available yet. 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.5/5.0
Behavior4/5

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

Annotations already cover readOnly/destructive/idempotent/openWorld, but the description adds genuine context beyond them: a cost hint ('Limits: 1 unit'), an availability constraint ('Spain not available yet'), and the meaning of the 'validated' tri-state return. It stops short of full behavioral detail but clearly enriches the annotation profile.

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-loads purpose, then organises the rest into labeled Inputs/Returns/Limits sections. Each sentence carries information (source, routing, cost, availability) with no filler.

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?

Covers purpose, usage routing, input source, and operational limits. An output schema exists so return values needn't be re-explained, yet the description still summarizes the validated tri-state and payload fields, leaving nothing an agent needs in order to call it correctly.

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 examples, enums, and per-field descriptions, so baseline is 3. The description's only added value over the schema is the cross-reference 'as lookup_company', which is a minor semantic link rather than new format or syntax detail.

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 verb+resource (validate a company's registered address) and names the backing data source (API Adresse / Base Adresse Nationale). It also distinguishes itself from 'search_companies', so an agent can tell it apart from siblings 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 Guidelines5/5

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

Explicitly states two positive use cases (confirm an address exists/is the company's, or geolocate it) and a negative one with a named alternative: 'Don't use it to find companies: call search_companies.' Nothing is 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