Skip to main content
Glama

Outil.io

Cancel contract

cancel_contract
Destructive

Annuler une demande de signature en cours (sent, viewed, expired) : statut cancelled, lien inactif. Un contrat signé ne s’annule pas.

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

Input Schema

NameRequiredDescriptionDefault
idYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real value beyond them: the resulting status becomes cancelled and the signing link is deactivated. It does not mention permission requirements or the effect of the optional reason field.

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 compact clauses, front-loaded with the action and its scope, followed by the exclusion rule. Nothing is redundant or padded.

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 the behavioral outcome and the precondition well, but leaves both input parameters unexplained, which is a meaningful gap given zero schema coverage.

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 both parameters (id, reason) are undocumented in the schema, so the description carries the full burden – yet it never mentions either parameter. An agent gets no guidance on what id refers to or how reason is used or surfaced.

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 (annuler) and resource (demande de signature / contrat) and bounds the operation with explicit statuses (sent, viewed, expired). It clearly separates this from a full deletion or from terminating a signed contract, though it does not explicitly contrast with the sibling delete_contract.

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?

It gives an explicit when-to-use condition (a signature request still in progress) and an explicit when-not (a contract already signed cannot be cancelled). No named alternative tool is offered for the signed case, which is the only gap.

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.