Skip to main content
Glama

checkers.fr — entreprises françaises

Derniers statuts (PDF)

statuts_entreprise
Read-onlyIdempotent

Renvoie le PDF des derniers statuts à jour déposés par une société (capital, objet, répartition des pouvoirs, clauses). Désignez-la par siren ou siret. Coût : 3 crédits.

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

Input Schema

NameRequiredDescriptionDefault
sirenNoSIREN de l’entreprise, 9 chiffres.
siretNoSIRET d’un établissement, 14 chiffres.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the cost of 3 credits and the guarantee that the returned document is the latest filed version. It does not say what happens if no statuts exist or how the PDF is delivered.

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 short sentences, front-loaded with what is returned, then how to designate the company, then cost. No redundant or decorative wording.

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 simple two-parameter read tool with full schema coverage and no output schema, the description covers purpose, input designation and cost. The only gap is delivery mechanics of the PDF and failure behavior when no statuts are on file.

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 both parameters are already documented with formats (9-digit SIREN, 14-digit SIRET). The description adds the meaningful clarification that either identifier is sufficient to designate the company, which is not evident from a schema where neither field is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Renvoie le PDF') tied to a specific resource ('derniers statuts à jour déposés par une société') and enumerates what the document contains (capital, objet, répartition des pouvoirs, clauses). This clearly separates it from siblings like comptes_annuels or rechercher_documents, though it never explicitly contrasts with them by name.

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?

It states how to identify the target company ('Désignez-la par siren ou siret'), which implies the retrieval use case, but gives no explicit when-to-use versus alternatives such as telecharger_document or rechercher_documents, and no prerequisites or exclusions.

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.

Resources