Skip to main content
Glama

Outil.io

Send quote

send_quote
Destructive

Figer, numéroter (DEV-AAAA-NNNN, sans trou) et publier un devis. Renvoie publicUrl (page d’acceptation : accepter avec signature / refuser + commentaire) et pdfUrl. N’envoie AUCUN e-mail : transmettre le lien soi-même (e-mail, WhatsApp…). Idempotent.

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": {
      "id": "<id>"
    },
    "name": "send_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the key behaviors: the return values (publicUrl acceptance page with signature/refusal, pdfUrl), the no-email delivery model, and idempotency — which materially matters given destructiveHint=true and reassures safe retries. It does not state that 'figer' makes the quote immutable afterwards or that cancel_quote is the escape hatch, leaving a gap in the destructive profile.

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, each front-loaded with the action, the outputs, and the delivery caveat. Every sentence earns its place, including the idempotency note.

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?

With no output schema, the description usefully names both returned URLs and describes the recipient-facing acceptance flow. It is nearly complete for a one-parameter mutation, with only the preconditions (allowed quote status) and post-freeze editability left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter 'id' with 0% schema description coverage and no type/meaning explanation in the description beyond the implicit context of 'un devis'. The agent must infer that it is the quote identifier, and nothing indicates whether it is the quote's numeric ID versus another object reference.

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 three specific verbs on a named resource: 'Figer, numéroter ... et publier un devis', plus the exact numbering format (DEV-AAAA-NNNN, sans trou). This is clearly distinct from create_quote (drafting) and cancel_quote/delete_quote, and an agent can tell what state transition happens 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 Guidelines4/5

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

Usage context is clear: it is the publishing/notification step for an existing quote, and the emphatic 'N’envoie AUCUN e-mail : transmettre le lien soi-même' steers the agent away from assuming delivery and toward the send_* messaging siblings. No explicit exclusions such as required quote status or a comparison with create_quote are given, 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.