Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get email sequence

get_email_sequence
Read-onlyIdempotent

Retrieve a Golden List's email sequence: each email's day, subject and body in order, plus sending status and enrolled, sent and replied counts. Reads only, no changes made.

Instructions

The Email Agent's sequence for a Golden List: each email's day, subject and body in order, plus whether sending is on and the enrolled, sent and replied counts. Reads only.

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_email_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
campaign_idNo

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, destructiveHint=false and openWorldHint=false, so 'Reads only' is largely redundant. However, the description adds genuine value by disclosing the shape of the returned data (ordered emails with day/subject/body, plus sending status and enrolled/sent/replied counters), which no output schema provides.

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?

A single front-loaded sentence with no filler; the resource comes first and the return contents follow. It is dense — several clauses stacked after a colon — but every clause carries 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?

For a zero-required-parameter read tool with no output schema, the description covers the essential gap by describing what comes back. The missing piece is parameter behavior and any routing guidance, which keeps it short of fully complete.

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?

The reported schema description coverage is 0%, and the description says nothing about account_id or campaign_id — not their meaning, defaults, or the fallback to the account's main golden list. The parameter semantics are left entirely to the schema (and the 'Golden List' reference is the only indirect hint).

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 resource (the Email Agent's sequence for a Golden List) and enumerates its contents — per-email day, subject, body, sending on/off, and enrolled/sent/replied counts — so an agent knows exactly what it retrieves. The verb is only implied ('Reads only'), but the retrieval intent is unmistakable and distinguishable from save_campaign_sequence.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_campaign_email or save_campaign_sequence. The agent must infer that this is the read counterpart to the save tool from the names alone.

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