Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get task

get_task
Read-onlyIdempotent

Retrieve a research task’s current answer, version, and allowed actions—or its original goal with a historical snapshot—plus optional sent-status history; read-only.

Instructions

One research task: its current answer with version and allowed_actions (pause, resume, cancel, retry), or the original goal when historical_snapshot=true. include_history=true adds bounded sent-status history and event metadata for past deliveries (no email bodies or receipts). Conference totals count roster entries, not distinct individuals. Sent status is not proof of inbox delivery. Reads only.

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>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYes
include_historyNo
historical_snapshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description reinforces it with 'Reads only.' Beyond that it adds real interpretive context an agent cannot get from structured fields: history is bounded and excludes email bodies and receipts, conference totals count roster entries rather than distinct people, and sent status is not proof of inbox delivery. These caveats about data meaning are the strongest part of the definition.

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?

The primary return shape is front-loaded in the first clause, with mode-switching parameters immediately after and caveats trailing. It is dense and telegraphic but nearly every sentence carries distinct information; the conference-totals note is the one line that feels tangential to a getter.

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

Completeness5/5

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

There is no output schema, so the description bears the full burden of describing returns, and it does: answer, version, allowed_actions, the historical variant, and the bounded history payload with its exclusions. Combined with annotations covering safety, an agent has everything needed to call this correctly.

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 description coverage is 0%, so the description must carry parameter meaning, and it does for two of three: include_history is defined as bounded sent-status history plus event metadata without bodies/receipts, and historical_snapshot is defined as returning the original goal instead of the current answer. goal_id is left unstated, though its required integer nature makes it largely self-evident.

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 names a specific verb+resource (retrieve one research task) and enumerates what comes back: current answer, version, and allowed_actions. It also states the alternative mode (original goal when historical_snapshot=true), which lets an agent distinguish this from artifact or listing tools. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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?

Usage is conveyed indirectly through parameter semantics: set historical_snapshot for the original goal, include_history for delivery history. The mention of allowed_actions (pause, resume, cancel, retry) hints at the action siblings but never says 'use cancel_task to cancel' or when this tool is the wrong choice. An agent can infer usage but gets no explicit when/when-not routing.

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