Skip to main content
Glama

Outil.io

Cancel quote

cancel_quote
Destructive

Annuler un devis envoyé, consulté, refusé, expiré ou accepté sans paiement : statut cancelled, lien public inactif, liens de paiement en attente fermés. Le numéro reste dans la séquence. Paiement reçu : rembourser d’abord.

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

Input Schema

NameRequiredDescriptionDefault
idYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantive effects beyond them: the quote moves to 'cancelled' status, its public link becomes inactive, and pending payment links are closed, while the quote number is retained in the sequence. It does not say whether cancellation is reversible, what permissions are required, or what happens when the refund precondition is unmet.

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?

Two dense, front-loaded sentences with no filler; the eligible statuses come first and the payment caveat last. The telegraphic French style is efficient, though the colon-separated effect list reads as shorthand rather than full explanation.

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

Completeness3/5

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

For a destructive mutation with no output schema, the description covers preconditions, resulting state, and side effects on links, which is the important part. However, with zero schema description coverage it leaves both parameters unexplained, which is a real gap for the 'reason' argument an agent must decide whether to populate.

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?

Schema description coverage is 0% for two parameters, and the description never mentions either one. The required 'id' is only implied by the resource being cancelled, and the optional 'reason' (a string up to 1000 chars) is completely undocumented, so an agent gets no guidance on whether to supply it or what it is used for.

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 states a specific verb (cancel) and resource (a quote), and even enumerates the eligible quote states (sent, viewed, refused, expired, accepted without payment). It does not distinguish itself from the sibling delete_quote or explain how cancellation differs from deletion, which keeps it below a 5.

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?

Clear when-to-use conditions are given by listing the statuses that qualify for cancellation, plus a prerequisite: if payment has already been received, refund first. It stops short of naming alternatives (e.g. delete_quote) or stating what to do for a quote that does not fall into any listed state.

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.