Skip to main content
Glama

siren_check

Validate French SIREN/SIRET numbers with Luhn checksum and La Poste exception, format identifiers, derive NIC and intra-EU VAT numbers offline for up to 100 entries.

Instructions

French SIREN (9) / SIRET (14) checksum validation (Luhn, La Poste exception), formatting, NIC, and the derived intra-EU VAT number. Up to 100 numbers. Offline: no register call. Costs 0.001 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": "siren_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYesSIREN/SIRET number(s), comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it discloses the 100-number batch cap, the offline/no-register nature, a per-success price of 0.001 USDC on Base via x402, and the exact failure mode (a 402 challenge returned when no payment key is present). The remaining gap is that it does not say what a failed checksum yields versus a successful one.

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?

Three dense sentences, front-loaded with what the tool validates and followed by operational constraints (batch size, offline, pricing, auth failure). No filler and nothing repeated from the schema.

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 single-parameter, annotation-free, output-schema-free tool, the definition covers cost, batching, offline behavior, and the payment-failure path. It stops short of describing the return payload (validity flags, formatted number, derived VAT), which an agent must infer.

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%, so the baseline is 3. The description still adds value beyond the schema by imposing the 'up to 100 numbers' limit and by clarifying that SIREN (9) and SIRET (14) inputs are both accepted through the single 'siren' parameter, which the schema alone does not convey.

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 uses a specific verb-plus-resource framing ('French SIREN (9) / SIRET (14) checksum validation') and enumerates the sub-functions it performs (Luhn, La Poste exception, formatting, NIC, derived intra-EU VAT). This is clearly distinguishable from sibling lookups such as fr_company or eu_vat, which do register/VIES work rather than offline checksum math.

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?

The definition gives a clear application context: offline validation of up to 100 comma-separated numbers with no register call. That implicitly steers an agent away from fr_company when no lookup is wanted, though it never explicitly names alternatives or states when to prefer a register-backed sibling instead.

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