Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List tasks

list_tasks
Read-onlyIdempotent

Lists research tasks and agent configurations with state filters and pagination so you can review progress and current answers without creating new work.

Instructions

Lists the account's existing research tasks and agent configurations, filtered by state and paged. Each row has its goal id, title, state, worker-step progress and, where a newer answer exists, current_answer_goal_id. Reads only; creates no work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.3/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 the safety profile is covered. The description still adds real value beyond them by describing the row shape (goal id, title, state, worker-step progress) and clarifying that current_answer_goal_id is only present when a newer answer exists. It does not explain pagination termination or row limits.

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 the core action and scope. The second sentence is dense but every clause (row fields, conditional current_answer_goal_id) conveys information an agent would otherwise have to discover at runtime.

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

Completeness4/5

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

For a two-parameter, non-destructive read tool with no output schema, the description covers the action, the filtering dimension, paging, and the returned row contents. The remaining gaps are minor operational details (page size, empty-state default, end-of-results detection).

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% and the description only says 'filtered by state and paged' without mapping to the parameters. It never explains that state accepts an enum with an empty-string default meaning unfiltered, nor what page indexing or page size means, so the agent must open the schema and guess at the empty-string semantics.

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 and resource ('Lists the account's existing research tasks and agent configurations') plus the two dimensions of scoping (state filter, paging). An agent can tell this is a read-only enumeration of task rows. It does not name a sibling it is distinct from, so it stops short of 5.

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 when-to-use guidance and no alternatives named. The only directional hint is 'Reads only; creates no work', which tells the agent what the tool will not do, not when to pick it over full_list or list_schedules.

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