Skip to main content
Glama

Outil.io

Create quote

create_quote

Créer un devis brouillon : lignes (désignation, quantité, prix unitaire HT, TVA ; ou productId/tier pour reprendre le catalogue), remise, acompte, validité, conditions. Totaux HT/TVA/TTC calculés. Lier contactId, prospectId ou dealId. Puis send_quote.

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": {
      "lines": "<lines>"
    },
    "name": "create_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoObjet du devis
linesYes
notesNo
termsNo
clientNoCoordonnées imprimées (reprises du contact si absent)
dealIdNoOpportunité CRM passée à won à l’acceptation
currencyNo
discountNoRemise globale HT
durationNo
contactIdNo
startDateNo
vatExemptNoMicro-entreprise : TVA non applicable, art. 293 B du CGI
prospectIdNo
validUntilNo
paymentTermsNo
validityDaysNoAlternative à validUntil (30 jours par défaut)
depositPercentNoAcompte demandé à l’acceptation
requireSignatureNo

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?

Annotations only declare write/non-destructive/closed-world, so the description carries real weight and delivers: it reveals the quote is created in DRAFT state (not sent), that HT/TVA/TTC totals are computed server-side, and that it can be attached to a contact, prospect or deal. It does not mention permission requirements, whether the draft can be retrieved later, or what identifier comes back.

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?

A single dense sentence that front-loads the verb and then clusters the payload logically (lines, discount/deposit/validity, CRM links, next step). Telegraphic style is efficient and every clause carries information, though the parenthetical line-item enumeration is slightly cramped.

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?

Missing.

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?

Coverage is only 39% across 18 parameters, so the description must compensate more than it does. It usefully groups the line-item alternative (free text fields versus productId/tier pulled from the catalogue) and names discount, deposit, validity, terms, and the three link IDs, but currency, name, notes, startDate, duration, vatExempt, requireSignature, paymentTerms and the whole client object are untouched.

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?

The description gives a specific verb and resource ("Créer un devis brouillon") and enumerates the substance of the resource: lines, discount, deposit, validity, terms. The draft qualifier and the closing "Puis send_quote" make its role distinct from the sending sibling, though it never explicitly contrasts itself with update_quote or get_quote.

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?

Usage context is clear: this is the draft-creation step of a two-step workflow, and "Puis send_quote" names the follow-up tool explicitly. There is no statement about when not to use it (e.g. to modify an existing quote) or about prerequisites such as needing a contact or catalogue product first.

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.