Skip to main content
Glama
Sign In

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

by com.fuentio
OverviewDiscussionsAdmin

List covered countries and ID formats

list_coverage
Read-onlyIdempotent

List the countries, ID formats and official sources Fuentio covers. Free, no key. Use it first when unsure whether a country or ID format is supported, or to explain coverage. Don't use it to check a company: call lookup_company or search_companies. Inputs: none. Example: list_coverage(). Returns: per country, status (available or planned), coverage level, ID formats with real examples and whether lookup works, regional registers, and sources with licence and update frequency. Limits: 0 units. Read-only. Covered today: France, Spain and United Kingdom. Search words: company registry, KYB, SIREN, RCS, Annuaire des Entreprises, société; BORME, Registro Mercantil, empresa, sociedad; Companies House, company number, Ltd, plc, LLP.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / CountryCoverage / properties / datasets
      Added value: +{
+  "default": [],
+  "description": "Data served beside the company records (e.g. France's public contracts, in review_report), each with its source, licence and update frequency.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Datasets",
+  "type": "array"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations' readOnly/idempotent hints, it discloses cost and auth ('Free, no key'), the quota ('Limits: 0 units'), the return shape per country (status, coverage level, ID formats with real examples, regional registers, sources with licence and update frequency), and the current live coverage set (France, Spain, United Kingdom). These are exactly the traits annotations cannot convey.

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 purpose and routing, then labelled sections (Inputs, Returns, Limits, Search words) that make it scannable. The trailing multilingual keyword block is long and largely redundant for an agent reader, which costs it the top score.

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?

Even though an output schema exists, the description pre-frames its contents, adds quota and coverage-state context the schema cannot express, and leaves no ambiguity about how or when to call a zero-parameter tool. Nothing needed for correct invocation is missing.

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?

The tool takes no parameters, so the baseline is 4. The description confirms this explicitly ('Inputs: none') and supplies a call example, which is the most an agent needs for a zero-argument tool.

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 and resource — listing the countries, ID formats and official sources covered — with a clear scope boundary ('Fuentio covers'). It explicitly disambiguates from siblings by name, so an agent can distinguish it from lookup_company or search_companies without opening either 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?

Gives explicit when-to-use ('Use it first when unsure whether a country or ID format is supported, or to explain coverage') and when-not with named alternatives ('Don't use it to check a company: call lookup_company or search_companies'). This is a complete routing rule.

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