Skip to main content
Glama
Sign In
Reedapt MCP server

Reedapt MCP server

Official
by Reedapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel a dub

cancel_dub
DestructiveIdempotent

Stops an unfinished dub and returns its reserved minutes. This irreversible action cannot be undone.

Instructions

Stops a dub that hasn't finished. Its reserved minutes are returned. This can't be undone.

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": {
      "dub_id": "<dub_id>"
    },
    "name": "cancel_dub"
  }
}

Input Schema

NameRequiredDescriptionDefault
dub_idYesThe dub's id, such as dub_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavior: reserved minutes are returned to the account, and the action is irreversible. It does not say what error or no-op results if the dub already completed, which is the one remaining behavioral gap.

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?

Three short sentences, zero filler, with the precondition and effect front-loaded before the irreversibility warning. Every sentence carries distinct 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 one-parameter cancellation tool with annotations covering safety and no output schema, the description covers purpose, side effect (minute refund), and irreversibility. A note on the outcome for already-finished dubs would make it 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 100% with a single required dub_id that the schema already documents with a format example. The description adds no additional meaning about the identifier, so baseline 3 applies since the schema does the work.

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?

"Stops a dub that hasn't finished" gives a specific verb and resource plus a scope precondition, which distinguishes it from read-only siblings like get_dub or list_dubs. It stops short of explicitly naming a sibling alternative, so it is clear but not maximally differentiating.

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 precondition "hasn't finished" implies when the tool applies, but there is no explicit guidance on what to do for finished or failed dubs, nor any named alternative (e.g. deleting vs. cancelling). Usage is inferable rather than stated.

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