Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

instructions_cancel

Cancel a running instruction while choosing whether to keep or delete already-collected responses. Use keepData to preserve results for later analysis or remove them entirely.

Instructions

Cancel a running instruction. keepData=true retains any responses already collected; keepData=false deletes them.

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": "instructions_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
keepDataNoKeep already-collected responses (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It explains the keepData branch and discloses the destructive consequence of keepData=false, which goes beyond the schema's default note. It adds useful behavioral context beyond what structured fields provide.

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, front-loaded with the primary action and no filler. Every sentence earns its place, covering both the operation and the key parameter behavior.

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 simple two-parameter cancel tool with no annotations and no output schema, the description covers the essential action, target scope, and the important data-retention behavior. It does not address edge cases like already-completed instructions or invalid ids, but those are not critical for tool selection.

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?

The description clarifies keepData by explaining what true and false do, adding meaning beyond the schema. However, the required id parameter remains semantically implicit as just an integer; its meaning is inferred from the tool name rather than explained.

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?

The description states a specific verb and resource: 'Cancel a running instruction.' This clearly distinguishes it from sibling cancel tools for scheduled and persistent instructions, and from instructions_rerun. The action and target are unambiguous.

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?

The description tells an agent when to use the tool: for a running instruction. It does not explicitly compare with alternatives like scheduled_instructions_cancel or persistent_instructions_cancel, but the 'running instruction' context is clear enough to route selection.

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

Deploy Server

Other Tools