siren_from_siret
Split a French SIRET into SIREN + NIC, checksum both (Luhn / La Poste), and compute the CGI 286 ter VAT key. No INSEE lookup. Paid $0.01 USDC Base x402.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
fr-legal-kit
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the computational nature of the tool and its cost, and explicitly states that no INSEE lookup occurs. However, with no annotations, it does not fully clarify side effects or whether the tool is read-only, though the described behavior implies a pure computation.
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?
The description is a single, concise sentence that packs in the key operations, the no-lookup caveat, and the cost. No unnecessary words or redundancy are present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the description lists the operations, it lacks critical context such as the expected input format and the structure of the output. Since there is no output schema, the return format should have been described for the tool to be used correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty with additionalProperties true, and the description does not specify the parameter name, type, or format for the SIRET value. An agent has no way to know how to pass the input to this 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?
The description clearly states the tool's specific operations: splitting a French SIRET into SIREN and NIC, checksumming both, and computing the VAT key. It also mentions 'No INSEE lookup', which helps differentiate it from potential external-lookup tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage context by noting there is no INSEE lookup and that the tool costs $0.01, but it does not explicitly explain when to choose this tool over sibling tools like 'vat_key' or 'check_siret'. More direct selection guidance would improve this score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.7/5.0
Disambiguation3/5
Many tools cover adjacent legal concepts such as down payments (acompte/arrhes), payment deadlines (due_date/due_eom/days_late), and identifier checks (check_siret/siren_from_siret/vat_key/eori), which can cause misselection. The descriptions do distinguish them clearly, but the sheer volume of overlapping categories still creates boundary confusion for an agent.
Naming Consistency4/5
All tool names use lowercase snake_case and are mostly short, readable French legal nouns or noun phrases, so there is a predictable stylistic pattern. The mix of French and English names and the occasional verb-led names like check_siret or siren_from_siret prevent a perfect score.
Tool Count1/5
With 68 tools, this server is far beyond the well-scoped 3-15 tool range and even beyond the 50+ extreme-mismatch threshold. Each tool is a tiny one-purpose helper, but the set as a whole is overwhelming and should be grouped into fewer, broader tools or split into multiple servers.
Completeness5/5
The tool surface covers an impressively broad range of French legal needs: statutory invoice mentions, payment penalties, holidays, VAT calculations, identifier checks, warranties, withdrawal rights, and dunning steps. There are no obvious dead ends, and mention_fields acts as a completeness checklist for required invoice mentions.