Skip to main content
Glama

Rouage

Commander la radiation d'une micro-entreprise

commander_radiation_micro
Destructive

À utiliser quand l'utilisateur veut fermer (radier) sa micro-entreprise ou auto-entreprise en France et a donné son accord pour transmettre ses coordonnées. Transmet à Rouage ses coordonnées et ses réponses, crée la commande et rend le prix et un lien de paiement par carte sur le site de Rouage, valable 2 heures. Ne prend aucun paiement et ne dépose rien : l'utilisateur paie par le lien puis complète son dossier sur le site. Ne convient pas aux sociétés (SAS, SARL, EURL, SCI).

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": {
      "prenom": "<prenom>",
      "nom": "<nom>",
      "email": "<email>",
      "telephone": "<telephone>",
      "arret_definitif": "<arret_definitif>",
      "activites": "<activites>",
      "salaries": "<salaries>",
      "fonds": "<fonds>",
      "regime": "<regime>",
      "date_cessation": "<date_cessation>",
      "accord": "<accord>"
    },
    "name": "commander_radiation_micro"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom de famille de l'utilisateur.
emailYesAdresse e-mail de l'utilisateur, où Rouage envoie le suivi du dossier.
fondsYesQue devient votre fonds ? ferme : il s'arrête avec l'activité ; vendu : il est vendu ; location_gerance : il est mis en location-gérance.
sirenNoSIREN de la micro-entreprise (9 chiffres), facultatif.
accordYestrue seulement si l'utilisateur vient d'accepter que ses coordonnées et ses réponses soient transmises à Rouage pour créer la commande.
prenomYesPrénom de l'utilisateur.
regimeYesÊtes-vous au régime de la micro-entreprise ? micro : oui ; reel : régime réel.
salariesYesAvez-vous encore des salariés ?
activitesYesToutes vos activités s'arrêtent-elles ? toutes : oui ; une_conservee : une activité est gardée.
telephoneYesNuméro de téléphone de l'utilisateur, au format français ou international.
date_cessationYesDate d'arrêt de l'activité, au format AAAA-MM-JJ, au plus tard un mois après aujourd'hui.
arret_definitifYesArrêtez-vous votre activité pour de bon ? oui : arrêt définitif ; pause : simple pause.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructive=true, openWorld=true and non-idempotent; the description adds crucial context: data is sent to a third party (Rouage), an order is created, a payment link valid 2 hours is returned, no payment is taken by the tool and nothing is filed — the user pays and finishes the dossier on the external site. This substantially reframes what 'destructive' means here and discloses the external transmission and time limit.

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?

Three front-loaded sentences: trigger first, then what happens, then exclusions. Slightly redundant in restating that the user pays via the link after saying no payment is taken, but the repetition usefully prevents a misread of the destructive annotation.

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 an 11-required-parameter commercial/legal tool with no output schema, the description covers the trigger, the consent precondition, the external side effects and even the return values (price, payment link, 2-hour validity). Only failure/error behavior and the source of each required field are left unstated.

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 description coverage is 100%, so each of the 12 parameters (including the enum meanings and the 'accord' consent flag) is already documented in the schema. The description reinforces the consent gate and the fact that user answers are transmitted, but adds no field-level semantics beyond that, so the baseline of 3 applies.

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 states a specific action (closing/radiating a micro-entreprise in France), the concrete effect (sending data to Rouage, creating an order, returning a price and a 2-hour payment link), and explicitly excludes companies (SAS, SARL, EURL, SCI). An agent can distinguish it from a general business-plan or services tool 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 Guidelines5/5

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

It gives a precise trigger condition (the user wants to close a micro-entreprise/auto-entreprise AND has agreed to transmit their details) plus an explicit exclusion (not for sociétés). The 'quand' and 'quand pas' are both stated, leaving little inference.

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