Skip to main content
Glama

Outil.io

Delete contract

delete_contract
Destructive

Supprimer un contrat BROUILLON.

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_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is an irreversible mutation. The description adds the draft-only scope constraint, which is real context beyond the annotations, but it does not say what happens on a non-draft contract (error vs. no-op) or whether confirmation is required.

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?

One short sentence with the key precondition front-loaded and no filler whatsoever. Brevity here is efficient rather than confusing, though the sentence is thin enough that it borders on under-specification.

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 one-parameter destructive tool with annotations covering the safety profile, the definition supplies the essential precondition, which may be sufficient to call correctly. It leaves gaps on the id's format, failure behavior for non-draft contracts, and any sibling alternative, and it is written in French while the rest of the tool surface is English.

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% and the single parameter 'id' (integer, exclusiveMinimum 0) is undocumented in the schema. The description only implies the id identifies a contract; it does not state type, positive-integer constraint, or that it must reference a draft contract, so it fails to compensate for the coverage gap.

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 names a specific verb and resource ('Supprimer un contrat') and adds the crucial qualifier 'BROUILLON' (draft), so an agent knows exactly which records this applies to. It does not, however, distinguish itself from siblings like cancel_contract or update_contract, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

The word 'BROUILLON' implies the precondition for use — only draft contracts are deletable — which is genuine usage guidance. There is no explicit statement about alternatives (e.g., cancel_contract for non-drafts) or what to do when the contract is not a draft.

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.