Skip to main content
Glama
Sign In
taap-mcp

taap-mcp

Official
by 402Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cancel_trigger

Disarm an active trigger by trigger ID for the owning trader only. Use it to stop a conditional or scheduled trade trigger when it is no longer needed.

Instructions

Disarm a trigger by trigger_id. Only the owning trader can cancel it.

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": {
      "trader_id": "<trader_id>",
      "trigger_id": "<trigger_id>"
    },
    "name": "cancel_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
trader_idYes
trigger_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose an authorization prerequisite (owning trader). It does not state whether the cancel is permanent, what happens to an already-fired trigger, or what a failed cancellation returns.

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, no filler, with the action front-loaded before the permission caveat. Every clause earns its place.

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 simple two-parameter mutation tool with no annotations or output schema, the description covers the core action and one precondition, but leaves trader_id undocumented and the post-cancellation state unspecified.

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%, so the description must compensate, but it only names one of the two required parameters (trigger_id) and adds no format or sourcing detail for either it or trader_id.

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?

States a specific verb pair (disarm/cancel) and resource (trigger), keyed on trigger_id, so the agent can distinguish it from set_trigger, list_triggers, and check_triggers. Sibling differentiation is implicit via the verb rather than explicit.

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 description supplies one real usage constraint – only the owning trader may cancel – which implies the required authorization context. It does not say when to prefer this over alternatives such as pause_trading or how to recover from an invalid trigger_id.

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