Skip to main content
Glama

Resume a Recipe Acceptance Activity

resume_recipe_activity
DestructiveIdempotent

Resume one approved supervised acceptance activity; this may spend credits and call external providers.

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": "resume_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

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=true, so the mutation and external-world profile is covered. The description adds genuinely new consequence information the annotations cannot express: the call may spend credits and may call external providers, which is exactly the kind of cost/side-effect warning an agent needs before invoking. It stops short of describing what resumption does to prior partial state.

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?

A single front-loaded sentence with no filler, and the cost warning sits in the most useful position after the verb-resource phrase. It is arguably too terse for a five-parameter destructive tool, but nothing present is wasted.

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?

A destructive, credit-spending, open-world operation with five undocumented required parameters and no output-schema-free explanation of what resumption returns or how a resumed run relates to the original. The existing output schema removes the need to describe return values, but the parameter and precondition gaps leave the definition inadequate for this complexity.

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

Parameters1/5

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

All five parameters (build_ref, revision, idempotency_key, handoff_ref, activity_ref) are required with 0% schema description coverage, and the description explains none of them. The meaning of handoff_ref and activity_ref in particular is completely opaque, and the description does nothing to compensate for the coverage gap.

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 ('Resume') plus a clearly scoped resource ('one approved supervised acceptance activity'), and the word 'one' bounds the operation to a single activity. It does not distinguish itself from siblings such as cancel_recipe_activity or run_recipe_acceptance, so an agent must infer the boundary from names alone.

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?

'Resume one approved supervised acceptance activity' implies a precondition (an activity already approved and previously started) and a singular scope, which is useful implied guidance. However, there is no explicit statement of when to use this instead of run_recipe_acceptance or when to prefer cancel_recipe_activity, so routing between the siblings is left to inference.

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