Skip to main content
Glama

kyb_check_fr

Verify a French company's KYB status from its SIREN/SIRET by checking identity, collective proceedings, intra-EU VAT validity, and sanctions, then returning a pass/review/fail verdict with flags.

Instructions

One-call KYB for a French company (SIREN/SIRET): Sirene identity and status, BODACC collective proceedings, VIES intra-EU VAT validity (derived FR number) and sanctions screening (OFAC, EU, FR, UK) of the legal name, with a pass/review/fail verdict and flags. Costs 0.01 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siren": "<siren>"
    },
    "name": "kyb_check_fr"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYesSIREN or SIRET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses a per-call cost (0.01 USDC on Base via x402) and the failure mode ('Without a payment key this tool returns the 402 challenge'), which is exactly the kind of side effect an agent must anticipate. It also states the output verdict taxonomy and flags, so the agent knows what a successful response yields.

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?

Two dense sentences, front-loaded with the resource and scope before listing checks, then closing with cost and failure behavior. No filler and nothing is buried mid-sentence that an agent would need to dig for.

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?

For a one-parameter aggregation tool with no output schema, the definition covers scope, underlying sources, verdict semantics, and payment preconditions well. The exact shape of the returned flags and any latency or rate-limit behavior are not described, which is a minor remaining gap.

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?

There is a single required parameter with 100% schema coverage, so the schema already explains 'siren: SIREN or SIRET'. The description restates the accepted identifier types but adds no extra semantics such as formatting rules, checksum validation, or behavior for a SIRET versus SIREN input, leaving it at the baseline-plus level.

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 names a specific verb and resource ('One-call KYB for a French company') and enumerates exactly what is checked: Sirene identity/status, BODACC proceedings, VIES VAT, and sanctions screening, ending in a pass/review/fail verdict. The 'French company (SIREN/SIRET)' scoping plus the presence of kyb_check_eu and kyb_check_uk siblings makes the jurisdiction boundary unambiguous.

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?

Usage context is clear: this is the France-jurisdiction KYB path, and the pricing/402 sentence implicitly tells an agent it needs a payment key before calling. It does not explicitly say 'for other jurisdictions use kyb_check_eu/uk' or when to prefer narrower tools like siren_check, so the exclusion guidance is inferred rather than stated.

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