Skip to main content
Glama
Sign In
@quackai/q402-mcp

@quackai/q402-mcp

Official
by quackai-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

q402_redstone_trigger_cancel

Cancel a RedStone trigger permanently using its triggerId. Stop scheduled actions from firing again.

Instructions

Permanently cancel a RedStone trigger so it never fires again. Authenticated by the Multichain API key. Use q402_redstone_trigger_list to find the triggerId.

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": {
      "triggerId": "<triggerId>"
    },
    "name": "q402_redstone_trigger_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletIdNoOptional. Defaults to server default wallet.
triggerIdYesRequired. The trigger id to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.14

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 full burden of behavioral disclosure. It discloses the irreversible effect ('never fires again') and the required authentication ('Authenticated by the Multichain API key'). It does not mention potential side effects like idempotency or error handling, but the key traits are covered.

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?

The description is concise, with two sentences that front-load the core purpose, then mention authentication and a cross-reference to a related tool. Every sentence earns its place, and there is no redundant information.

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 cancellation tool with no output schema and no annotations, the description covers the essential points: what it does, permanence, auth, and how to find the identifier. It is complete enough for an agent to use it correctly, though it could mention what happens if the trigger doesn't exist.

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 100%, so the baseline is 3. The description adds a useful hint that the triggerId can be found via q402_redstone_trigger_list, giving context for obtaining the value, but it does not elaborate further on parameter details beyond what the schema provides.

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 clearly states the tool's purpose with a specific verb and resource: 'Permanently cancel a RedStone trigger so it never fires again.' This distinguishes it from sibling tools like trigger_create and trigger_list, making it unambiguous which operation it performs.

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 provides clear context for use by stating the action's permanent nature and authentication requirement, and it explicitly directs the user to q402_redstone_trigger_list to find the triggerId. It lacks explicit exclusions (e.g., when not to use), but the guidance is sufficient for a cancellation tool.

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