Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get prospect list

get_prospect_list
Read-onlyIdempotent

Download an Excel prospect or ICP list, shared campaign list, or research-task workbook to review saved contact coverage; it starts no research and sends no messages.

Instructions

An Excel download of the user's main Golden List (prospect or ICP list), or another list they own or that was shared with them (campaign_id), or one research-task workbook (goal_id). A saved snapshot can include contacts whose enrichment is unfinished; the result gives actual coverage. Starts no research and sends nothing.

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

Input Schema

NameRequiredDescriptionDefault
goal_idNo
config_idNo
campaign_idNo

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 cover read-only, idempotent, non-destructive, closed-world, so the bar is lower, and the description still adds real behavior: snapshots may contain contacts with unfinished enrichment and the result reports actual coverage, plus an explicit side-effect disclaimer. It does not mention permissions or sharing/auth requirements for lists shared with the user.

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?

Three dense sentences, front-loaded with the resource and the selector mapping, and the parenthetical id hints tie directly to schema properties. The first sentence is a long run-on with stacked alternatives, but no sentence is filler.

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 three-optional-parameter read tool with no output schema, the description covers what is returned (Excel workbook), the selectors, and the no-side-effect guarantee. The remaining gap is the undocumented config_id and the fact that the all-params-omitted default is only implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning; it explains campaign_id (owned or shared list) and goal_id (research-task workbook) well. However, config_id — the third parameter — is never mentioned anywhere, leaving an agent to guess its role.

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+resource: an Excel download of a prospect/ICP list, with three selection modes (main Golden List, a list by campaign_id, or a research workbook by goal_id). It is distinguishable from list-style siblings because it emphasizes downloading a workbook, though it never explicitly contrasts with read_golden_list or full_list.

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?

Gives clear conditions for each selector (own/shared list → campaign_id, research task → goal_id, otherwise the main Golden List) and adds a negative boundary: 'Starts no research and sends nothing.' No explicit exclusion relative to similarly named siblings like read_golden_list is given.

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