Skip to main content
Glama

Outil.io

Delete quote

delete_quote
Destructive

Supprimer un devis BROUILLON (jamais numéroté). Un devis envoyé se conserve : cancel_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": {
      "id": "<id>"
    },
    "name": "delete_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the substantive precondition that only unnumbered drafts qualify, which prevents a destructive misapplication. It does not cover irreversibility, cascading effects, or required permissions, so it stops just short of full disclosure.

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?

Two short clauses, zero filler, with the restrictive scope front-loaded before the alternative. Nothing could be removed without losing a constraint.

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 single-parameter destructive delete with no output schema, the description supplies the one fact an agent most needs: the draft-only guard. Minor gap is the unstated meaning of 'id', but otherwise nothing essential is 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?

One required parameter ('id') with 0% schema description coverage; the description never says whose id it is (quote id) or what a valid draft id looks like. The 'BROUILLON' qualifier indirectly constrains which ids are acceptable, which is more than nothing but not real parameter documentation.

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?

States a specific verb+resource ('Supprimer un devis') plus a narrowing scope ('BROUILLON (jamais numéroté)'). The final clause routes the sent-quote case to cancel_quote, so an agent can distinguish this from its closest sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit when-to-use (draft quotes only, never numbered) and when-not (sent quotes are preserved) with the named alternative 'cancel_quote'. The selection condition is fully stated rather than implied.

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.