Skip to main content
Glama

Cancel a Recipe Acceptance Activity

cancel_recipe_activity
DestructiveIdempotent

Cancel one supervised acceptance activity. Cancellation is irreversible.

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": {
      "build_ref": "<build_ref>",
      "revision": "<revision>",
      "idempotency_key": "<idempotency_key>",
      "handoff_ref": "<handoff_ref>",
      "activity_ref": "<activity_ref>"
    },
    "name": "cancel_recipe_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
handoff_refYes
activity_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/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 largely covered; 'Cancellation is irreversible' reinforces rather than contradicts that. However, the description never says what happens to in-flight or already-completed work, whether compensation or billing effects occur, or whether the call fails on an already-cancelled activity.

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

Conciseness4/5

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

Two sentences, front-loaded, with zero filler or repetition. The concision borders on under-specification rather than being genuinely tight, which keeps it below a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with five required, undocumented, opaque parameters, the description omits the preconditions and failure modes an agent needs. An output schema exists, so return values need not be explained, but the input-side and pre-commitment guidance is missing.

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% across five required parameters, so the description carries the full burden but explains none of them: build_ref, revision (a 64-hex digest), handoff_ref, activity_ref, and idempotency_key are left to inference from names alone. Only the 'irreversible' note indirectly motivates the idempotency_key, and even that connection is unstated.

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 (cancel) and a specific resource (one supervised acceptance activity), and the singular 'one' signals that a single activity_ref is targeted. It does not name the obvious counterpart resume_recipe_activity, so sibling differentiation is left implicit despite the name being available.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to cancel versus resume or let an activity finish, no statement of prerequisites (which values must come from a prior run or handoff), and no indication of what state the activity must be in for cancellation to succeed. Only the word 'supervised' hints at context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources