Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get full list

full_list
Idempotent

Retrieves the complete list of people matched by a find_people search when initial results were partial, using its goal_id to rerun the same request and return up to 200 people per company.

Instructions

Everyone a find_people search (its goal_id) matched, when it returned only part of them: reruns the same request for everyone who matched, up to 200 people per company, and returns the complete list in the find_people shape, usually within one to three minutes. Each call returns within about 30 seconds: the list when it has finished, otherwise status still_running with progress (a one-line message for the person waiting) and next_step, and a repeat call with the same goal_id returns the same list. The earlier full_list figure counted matches before screening, so the result is usually somewhat smaller (coverage.returned against coverage.full_list.people). People already delivered are not charged again. One search has one full list, so a repeat call while status is still_running never starts or charges a second. status upgrade_required, credits.exhausted or coverage.held_for_credits above 0 mean credits are used up; upgrade_url is the plans page. coverage.deep_search lists people it could not place. The account owner is emailed a summary with the workbook. Each result has view_in_producerspark and reply_must_end_with. In supporting chats the people also appear as cards with headshots; the cards carry no emails. No prospect outreach.

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": "full_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare it is non-read-only, open-world, idempotent and non-destructive. The description goes well beyond that: per-call ~30s latency with 1–3 minute overall completion, the still_running/progress/next_step protocol, credit exhaustion signals (status upgrade_required, credits.exhausted, coverage.held_for_credits) plus upgrade_url, the billing rule that already-delivered people are not charged again, and a no-double-charge guarantee per search. It also discloses that the final count is usually smaller than the earlier full_list figure because screening happens first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is valuable but the packaging is poor: long run-on sentences, an awkward lead fragment, and status/billing/output-detail threads interleaved rather than grouped. Side details such as chat cards with headshots carrying no emails, the account-owner email summary with a workbook, and 'No prospect outreach' dilute the core guidance without being clearly essential.

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, and the description carries that burden well: it names the return shape (find_people shape), the status field values, next_step, coverage.returned vs coverage.full_list.people, coverage.deep_search, credits, upgrade_url, and per-result fields view_in_producerspark and reply_must_end_with. For a long-running, credit-consuming job, this is enough for an agent to call it and interpret the result 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?

With one parameter at 0% schema description coverage, the description does the explanatory work: goal_id is the identifier of the originating find_people search, and reusing the same goal_id is guaranteed to return the same list. What it does not say is where an agent obtains that goal_id (presumably from the find_people response), leaving one small inference.

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 concrete operation — rerunning a find_people request identified by its goal_id to obtain everyone who matched, up to 200 people per company, returned in the find_people shape. It distinguishes itself from find_people by the 'when it returned only part of them' framing. The opening is a grammatical fragment ('Everyone a find_people search ... matched, when it returned only part of them:'), which costs a little clarity but the intent is recoverable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is explicit: use this after a find_people search returned only a partial result, passing that search's goal_id. It also disambiguates repeat behavior (same goal_id returns the same list; a repeat while still_running starts nothing new). It does not spell out when not to use it, e.g. when find_people already returned everything, so it falls short of a full when/when-not treatment.

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