Skip to main content
Glama
Sign In

Agent Data Tools: Company and VAT check

by io.github.Nutshell2000
OverviewDiscussionsAdmin

French company lookup, Sirene register

fr_company
Read-only

French company by SIREN (552032534), SIRET or VAT number (FR27552032534), or by name, live from the State's company search API (INSEE Sirene and the RNE): name, acronym, legal form, active or ceased, creation date, NAF industry code, workforce band, company size category, establishments, head office address, VAT number. Use to verify a French customer or supplier. Register facts only, not a credit report. Example: siren=552032534. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "fr_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoWith name: only companies whose head office is in this town
nameNoCompany name to search for, instead of siren: up to 10 active companies
limitNoMatches for a name search (1-10, default 5)
sirenNoSIREN (9 digits), SIRET (14 digits) or French VAT number FR… (give siren or name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-idempotency, and the description reinforces both coherently: 'reads or computes only and changes nothing' and 'each call is charged, so repeats are not free', explaining why idempotency is false. It also adds pricing ($0.01/call, 25 free, failed calls free) and the payment path (x402 USDC or card key at /credits), which no annotation covers; remaining gaps are rate limits and error semantics.

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?

Purpose, identifier formats, and returned fields are front-loaded, and pricing sits at the end where it belongs. A few clauses are redundant ('Reads or computes only and changes nothing' re-states readOnlyHint) but nothing is seriously wasteful.

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?

With no output schema, the description carries the burden of describing returns and does so via an explicit field list (legal form, status, NAF code, workforce band, establishments, head office, VAT). Payment and cost behaviour are disclosed; only pagination and multi-match behaviour for name searches are left to the schema.

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%, so all four parameters are already documented, and the description largely restates the SIREN/SIRET/VAT formats already in the schema. The concrete example values (552032534, FR27552032534) add a small amount of format confidence but not new meaning.

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 ('French company') along with the identifier formats accepted and the upstream registers (INSEE Sirene, RNE), plus an enumerated field list. The 'French' jurisdiction qualifier lets an agent separate it from the other national company lookups among 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 Guidelines4/5

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

Gives an explicit use case ('verify a French customer or supplier') and a clear negative boundary ('Register facts only, not a credit report'), which is exactly the kind of when-not guidance that prevents misuse. It stops short of naming a sibling to route to for enrichment or credit-style checks.

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

All Agent Data Tools: Company and VAT check 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