Skip to main content
Glama

Rouage

Commander un business plan

commander_business_plan
Destructive

À utiliser quand l'utilisateur veut commander à Rouage un business plan prévisionnel à présenter à une banque et a donné son accord pour transmettre ses coordonnées. Transmet à Rouage ses coordonnées et la nature du projet, 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 rédige pas le business plan dans la conversation : l'utilisateur paie par le lien puis décrit son projet dans le questionnaire du site.

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>",
      "projet": "<projet>",
      "accord": "<accord>"
    },
    "name": "commander_business_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom de famille de l'utilisateur.
emailYesAdresse e-mail de l'utilisateur, où Rouage envoie le suivi du dossier.
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.
projetYesNature du projet. creation : création d'une entreprise ; reprise_fonds : reprise d'un fonds de commerce ; autre : rachat de titres, société existante ou autre cas.
telephoneYesNuméro de téléphone de l'utilisateur, au format français ou international.

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?

Beyond the annotations, it explains that the tool transmits contact details and project type to Rouage, creates the order, returns a price and a card payment link valid for two hours, and does not collect payment itself. It also tells the user what happens next: they pay via the link and then describe the project in the site questionnaire.

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 front-loaded with the usage condition, then states the action, then the key behavioral boundaries and next step. Every sentence adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter order-creation tool with no output schema, it explains the external side effect, the returned price and payment link, the link validity, and the post-payment questionnaire step. It is complete enough for an agent to call it correctly and set user expectations.

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?

The input schema has 100% description coverage, including the consent flag and project enum, so the schema already carries most parameter meaning. The description adds only the general fact that contact details and project nature are transmitted, without adding field-level semantics beyond the schema.

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 verb and resource: ordering a forecast business plan from Rouage to present to a bank. It clearly distinguishes this from unrelated sibling tools and from drafting the plan inside the conversation.

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?

It gives an explicit trigger—when the user wants to order the plan and has consented to transmit their details—and clarifies what the tool does not do: take payment or write the business plan. It does not route the agent to any alternative for payment or drafting, but the when-to-use and when-not conditions are clear.

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