Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Resume task

resume_task
Idempotent

Resume paused, user-authorized work within its existing scope and budget by supplying goal ID, expected version, idempotency key, and reason.

Instructions

Resumes paused, user-authorized work within its existing scope and budget.

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": {
      "goal_id": "<goal_id>",
      "expected_version": "<expected_version>",
      "idempotency_key": "<idempotency_key>",
      "reason": "<reason>"
    },
    "name": "resume_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
goal_idYes
idempotency_keyYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds genuinely new behavioral context: the resume stays 'within its existing scope and budget', so no scope expansion occurs. It omits the optimistic-concurrency behavior implied by expected_version and what happens on a version mismatch.

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. It is tight, though at this brevity it leaves required call details unaddressed rather than being padded.

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 mutating tool with four required undocumented parameters, no output schema, and a version-precondition contract, the description is too thin. It does not say what a successful resume returns, whether approval is re-checked, or how failures (stale version, insufficient budget) surface.

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% for four required parameters, and the description compensates for none of them. Nothing explains goal_id, the version-precondition semantics of expected_version, the idempotency_key contract, or the role of reason, which are exactly the fields an agent must supply correctly.

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?

The description gives a specific verb ('Resumes') and a defined object ('paused, user-authorized work'), which is clearly the inverse of pause_task and distinct from cancel_task or retry_task. It stops short of naming the task resource itself or differentiating explicitly from retry_task, which also restarts work.

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?

'paused' implies a precondition, and 'user-authorized' hints at an approval gate, but the description never states when to call this versus retry_task or cancel_task, nor what to do if the task is not paused. Usage is inferable rather than instructed.

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