Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Read Golden List

read_golden_list
Read-onlyIdempotent

Retrieve saved contacts from the main Golden List or a specified campaign list in one call, including emails, verification, and enrichment fields; set include_rows=false to return counts only.

Instructions

Every saved contact on the main Golden List, or another accessible list (campaign_id), in one call: emails, verification and enrichment fields. include_rows=false returns counts only. Starts no research, enrollment or sending.

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

Input Schema

NameRequiredDescriptionDefault
config_idNo
campaign_idNo
include_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds beyond that by promising a single-call full fetch and detailing the counts-only mode. The explicit negative guarantee about not starting research, enrollment or sending is exactly the kind of consequence disclosure annotations cannot express.

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?

Three short clauses, no filler, and the core capability plus scope is front-loaded before the mode switch and the side-effect disclaimer. Every sentence carries distinct information.

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?

With no output schema, the description does the work of indicating what comes back (contact rows with emails, verification and enrichment fields, or counts only), which is adequate for a read tool whose annotations cover safety. The remaining gap is the unexplained config_id and no sense of scale or truncation limits on a full-list fetch.

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 description coverage is 0%, so the description must carry the parameter burden: it explains campaign_id as selecting an alternate accessible list and explains include_rows=false as returning counts only. The third parameter, config_id, is never mentioned, leaving one of three parameters entirely undocumented.

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: reads 'every saved contact' from the 'main Golden List' or another list identified by campaign_id, and enumerates the field families returned (emails, verification, enrichment). It is clear what the tool returns and how it differs from a list-of-lists reader, though it never names the sibling tool it competes with.

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 implied rather than stated: the description signals a bulk fetch of all contacts and rules out side effects ('Starts no research, enrollment or sending'), which usefully narrows intent. However, there is no explicit instruction on when to choose this over list_golden_lists or get_prospect_list, and no prerequisite/auth guidance for 'another accessible list'.

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