Skip to main content
Glama

annuler_ecriture

Read-only

Cancels a pending PLC write request using its token, so an approved but not yet executed write is withdrawn before it reaches the controller.

Instructions

Annule une demande d'écriture en attente.

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": {
      "jeton": "<jeton>"
    },
    "name": "annuler_ecriture"
  }
}

Input Schema

NameRequiredDescriptionDefault
jetonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

The description says the tool cancels a pending write request, which is a state-changing operation, while the annotations declare readOnlyHint=true. That is a direct inconsistency about side effects. Beyond this, nothing is said about permissions, what happens if the request is not pending, or whether the cancellation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded sentence with no wasted words. The brevity is efficient but tips into under-specification, since nothing beyond the bare action is conveyed.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for a tool that cancels a pending write, the definition leaves the token semantics unexplained and never reconciles the state-changing action with the read-only annotation, leaving an agent without enough to call it confidently.

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?

The single required parameter 'jeton' has no schema description (0% coverage), and the description says nothing about it — whether it identifies the pending request, a session, or an authorization token. With only one parameter the burden is small, but the description adds no meaning whatsoever.

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 and object ('Annule une demande d'écriture en attente'), so an agent knows it cancels a queued write request rather than performing one. It does not, however, distinguish itself from the obvious sibling 'confirmer_ecriture', which is the natural counterpart action.

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

Usage Guidelines2/5

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

There is no guidance on when to cancel versus confirm a pending write, nor any precondition such as the request having to be in a pending state or still valid. The intended use is only inferable from the verb 'annule'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.