Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get Email Agent status

get_email_agent_status
Read-onlyIdempotent

Check whether an email agent is on or off for a list or campaign and review enrolled, sent, queued, sending, uncertain, failed, skipped, and replied counts. Read-only; sends nothing.

Instructions

The Email Agent's current state for a list: on or off, and its enrolled, sent, queued, sending, uncertain, failed, skipped and replied counts, with the same status paragraph its email replies use. Reads only; 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_email_agent_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNo
campaign_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the 'reads only; sends nothing' sentence largely restates structured data. The description does add genuinely new behavioral context: the status paragraph mirrors what the Email Agent emits in its email replies, and the exact counter set is disclosed. It does not say what happens when both filters are null or whether results are scoped per campaign versus per config.

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?

It is a single front-loaded sentence with no filler, and the operative constraint lands at the end. The long comma-separated counter enumeration makes it denser than necessary and slightly harder to parse than a short list, keeping it below the top mark.

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

Completeness3/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 right thing by enumerating the returned counters and the included status paragraph. However, for a tool whose only two inputs are optional identifiers, the absence of any targeting semantics leaves a material hole for an agent deciding how to call it.

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 neither parameter appears by name in the description; the phrase 'for a list' only vaguely gestures at campaign_id. With two optional, mutually ambiguous identifiers and no guidance on precedence, defaults, or null behavior, the description leaves the caller guessing how to target the right agent. This is a real gap that the schema does not compensate for.

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 concrete resource (the Email Agent's state for a list) and enumerates the exact metrics returned: on/off plus enrolled, sent, queued, sending, uncertain, failed, skipped and replied counts. It is clearly a read of agent status rather than an action on the agent, which separates it from siblings like pause_email_agent. It never names a sibling explicitly, so it falls short of a 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 statement of when to call this versus pause_email_agent, ask_email_agent, or get_email_sending_settings, nor any prerequisite or ordering guidance. 'Reads only; sends nothing' is a safety clarification rather than usage guidance. The agent must infer the calling context entirely.

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