Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Pause task

pause_task
Idempotent

Pauses future work on a task when its allowed actions permit. External operations already started still need reconciliation.

Instructions

Pauses future work on a task when its allowed_actions permit. External operations already started still need reconciliation.

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

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a mutating, idempotent, open-world, non-destructive operation. The description adds useful behavioral context beyond that: it only pauses future work, while already-started external operations still require reconciliation. That nuance matters for an agent reasoning about side effects.

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?

The description is two short sentences with no wasted wording. The core action and the important side-effect caveat are front-loaded and easy to scan.

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

Completeness3/5

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

For a mutating task-control tool with four required parameters, no output schema, and no schema descriptions, the definition covers purpose and side effects but leaves parameter semantics and alternative-tool guidance incomplete. It is usable but not fully self-contained.

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%, so the description must carry the burden of explaining the four required parameters. It does not mention goal_id, expected_version, idempotency_key, or reason, nor does it explain their roles in pausing safely or idempotently.

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 states a specific verb and resource: it pauses future work on a task. It also scopes the effect to future work, which helps distinguish it from cancel-like behavior, but it does not explicitly name or differentiate against siblings such as cancel_task or resume_task.

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 phrase "when its allowed_actions permit" gives an eligibility condition, implying the tool should be used only for tasks whose state allows pausing. However, it does not explain when to choose pause_task over alternatives like cancel_task or when not to use it.

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