Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Update email sending settings

update_email_sending_settings
Idempotent

Change the account's daily sending limit and weekend sending setting for every campaign, moving waiting first emails to the new schedule and returning the updated settings.

Instructions

Changes the account's sending days or daily limit for every campaign. Waiting first emails move onto the new days. Returns the settings in the get_email_sending_settings shape. A 400 error names a value outside what the account allows.

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

Input Schema

NameRequiredDescriptionDefault
daily_limitNoMost emails the account sends in a day.
send_on_weekendsNotrue to send every day, false for Monday to Friday only.

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 non-read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: the change is account-wide across every campaign, waiting first emails are migrated onto the new days, and an out-of-range input surfaces as a 400 error. What it omits is what happens to a parameter that is passed as null versus omitted.

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, front-loaded with the scope and effect, then side effects, then return/error behavior. No filler and nothing repeated from the schema.

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 two-parameter account-wide mutation with annotations already covering the safety profile and no output schema, this is nearly complete: it explains the blast radius, deferred effects, return shape via a named sibling, and error behavior. The one missing piece is the explicit null/no-op semantics for optional fields.

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 100% and both properties already document daily_limit and the send_on_weekends semantics, so baseline is 3. The description reinforces the scope ('for every campaign') and notes that invalid values are rejected with a 400, but it does not resolve the important ambiguity of whether a null/omitted field leaves the existing setting unchanged.

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 ('Changes the account's sending days or daily limit') and scopes it explicitly with 'for every campaign', which separates it from the per-campaign siblings. The link to get_email_sending_settings as the shape of the returned settings also hints at the read/write split, though it stops short of naming it as the read alternative.

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: an agent can infer this is the write counterpart to get_email_sending_settings because the return shape is named. There is no explicit 'use this instead of X when...' or statement of prerequisites, and the sibling shift/pause tools are not addressed at all.

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