Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Cancelar diagnóstico de IA

cancel_ai_diagnosis
Destructive

Cancels an in-progress AI diagnosis; set confirm to true to proceed.

Instructions

Cancela um diagnóstico em andamento. Exige confirm: true.

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

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the danger profile is known. The description adds a genuinely useful confirmation gate, but says nothing about what cancellation actually does to the diagnosis — whether it is discarded, resumable, or what error occurs if the diagnosis is not in progress.

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 sentences, zero filler, with the action stated first and the precondition immediately after. Nothing could be removed without losing information.

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, non-idempotent mutation with no output schema and no parameter documentation, the definition covers the action and the safety gate but omits outcome and failure behavior. It is minimally sufficient rather than complete.

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?

Schema coverage is 0% and neither parameter is documented in the schema. The description partially compensates by explaining the required semantic of `confirm` (must be true), but the `id` parameter is never explained beyond naming the diagnosis being canceled, leaving half the parameters undocumented.

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 resource ('Cancela um diagnóstico' / cancel a diagnosis) and scopes it to one that is 'em andamento' (in progress), which distinguishes it from the get/create diagnosis siblings. It does not, however, name any sibling explicitly.

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?

Usage is implied by the qualifier 'em andamento' — only in-progress diagnoses can be canceled — and a precondition is given ('Exige confirm: true'). There is no statement of what to do instead when the diagnosis has finished, nor any pointer to alternatives.

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