Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Pause Email Agent

pause_email_agent
Idempotent

Pauses Email Agent sending for a Golden List while keeping enrolled people in place; no emails are sent or deleted.

Instructions

Stops the Email Agent sending for a Golden List. Enrolled people keep their place. Nothing is sent or deleted.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "pause_email_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
campaign_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so safety and repeat-call behavior are covered. The description adds genuinely new behavior: enrolled people keep their place and nothing is sent or deleted, which tells the agent the pause is state-preserving rather than a purge. It does not say how to resume or whether the pause covers all campaigns vs one.

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 sentences, the action front-loaded, with zero filler. Each sentence contributes a distinct fact: what stops, what is preserved, and what is not affected.

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?

For a mutation-style pause with no output schema, the description covers the essential state guarantee but leaves gaps: no resume path, no statement of scope (one campaign vs account-wide), and no parameter guidance despite low schema coverage. Adequate to call safely, not 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?

Schema description coverage is reported as 0% and the description mentions no parameters at all. account_id, campaign_id and the required idempotency_key have to be understood entirely from the schema, and the description gives no hint about how a Golden List is targeted or what the idempotency key protects against.

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: 'Stops the Email Agent sending for a Golden List', which is more precise than a bare 'pause'. It is not explicitly distinguished from the sibling pause_campaign_sending, but the 'Email Agent / Golden List' scoping gives the agent enough to tell the targets apart.

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 only implied: you pause when you want sending to stop without losing enrollees. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. pause_campaign_sending, pause_task), so the agent must infer the choice from scope wording 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