Skip to main content
Glama

Outil.io

Create contract

create_contract

Créer un contrat brouillon depuis un modèle (templateKey / templateId + variables) ou un HTML. Charte et mentions du prestataire, client du contact ou du devis lié remplis d’office. Puis request_signature.

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

Input Schema

NameRequiredDescriptionDefault
htmlNoContrat HTML libre (h1-h3, p, ul/li, strong, table) avec {{variables}}
nameNo
dealIdNoModèle personnalisé (ressource contract_templates)
signerNo
quoteIdNoDevis lié : prix, objet et client repris
contactIdNoModèle personnalisé (ressource contract_templates)
variablesNoValeurs : object, price, duration, startDate, deliverables, paymentTerms, client.{name,company,address,siret}…
templateIdNoModèle personnalisé (ressource contract_templates)
templateKeyNoModèle intégré (prestation-services par défaut) : list_contract_templates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-destructive, closed-world), it adds meaningful behavior: the contract is created as a DRAFT, charter/provider mentions and the client from contact or linked quote are auto-filled, and this is a prerequisite to request_signature. It does not describe what identifier or object is returned, but that gap is minor.

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?

Terse and front-loaded: purpose first, then the auto-fill behavior, then the next step. Every clause carries information; only the mid-sentence enumeration of auto-filled fields is slightly dense.

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 9-parameter, nested-object tool with no output schema and no required parameters, the description covers the primary call patterns and the workflow dependency on request_signature. It does not spell out parameter combinations/requiredness, but the schema covers most of that, so it is adequately complete.

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?

Adds real meaning over the 78%-coverage schema by explaining how templateKey (built-in, default prestation-services), templateId (custom template), and variables combine, versus the html path, and that the client is auto-derived from contactId/quoteId. The nested signer object is not addressed, so it is not a 5.

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?

States a specific verb and resource ('Créer un contrat brouillon') and distinguishes the two creation modes (template via templateKey/templateId + variables, or raw HTML). An agent can tell what will be produced without opening the schema, though sibling differentiation relies mostly on the mention of request_signature.

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?

Gives clear context on the two supported pathways (template-based vs HTML) and routes the agent to the follow-up step ('Puis request_signature'). It lacks explicit when-not-to-use guidance or exclusions, which keeps it short of a 5.

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.