Skip to main content
Glama
Sign In

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Geplante Sendung abbrechen

schedule_cancel
Destructive

Bricht eine geplante Sendung ab und gibt die dafür reservierte Summe im Wallet wieder frei. Die scheduleId liefern letter_schedule und schedule_list. EN: Cancels a scheduled send and releases the amount reserved for it in the wallet. letter_schedule and schedule_list return the scheduleId.

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": {
      "scheduleId": "<scheduleId>"
    },
    "name": "schedule_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNotrue liefert die Summe, die frei würde, ohne die Planung abzubrechen. EN: true returns the amount that would be released, without cancelling the schedule.
reasoningNo
scheduleIdYesDie abzubrechende Planung. EN: The schedule to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds the non-obvious business effect: funds reserved in the wallet are released. That is real behavioral value beyond the annotation. It does not explicitly state irreversibility or what happens on an already-cancelled schedule, so a 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core message is front-loaded and tight, but the full German text is duplicated verbatim in English, roughly doubling the length without adding information. Two sentences earn their place; the second pass is pure repetition.

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 destructive single-parameter mutation with no output schema, the description covers the effect, the fund release, and how to obtain the id. It could still clarify whether dryRun's returned amount is the only output and how already-cancelled schedules are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, so the description should carry some weight; it adds genuine sourcing information for scheduleId ('letter_schedule and schedule_list return the scheduleId') that the schema's 'The schedule to cancel' does not. The undocumented 'reasoning' parameter is left entirely unexplained in both places.

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?

States a specific verb and resource ('cancels a scheduled send') plus its concrete side effect ('releases the amount reserved for it in the wallet'). It also names the sibling tools that produce the required identifier, so an agent can distinguish it from letter_schedule, schedule_list, and order_cancel without opening a schema.

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?

Gives clear prerequisite context by naming letter_schedule and schedule_list as the sources of the scheduleId, which is exactly the routing an agent needs before calling. It stops short of stating exclusions (e.g. when to prefer order_cancel or what to do if the schedule already fired).

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

All FrankKi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources