Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get email sending settings

get_email_sending_settings
Read-onlyIdempotent

Retrieve email sending settings to check send status, limits, mailbox readiness, authentication, queued sends, and deliverability. Use it to diagnose paused sending or mailbox readiness issues.

Instructions

The account's sending settings: whether sending is on, send_on_weekends, the daily limit and each mailbox's limit, minutes between sends, sending hours, stop on reply, and each connected mailbox with whether it is ready (and why not), in rotation, SPF/DKIM/DMARC, queued sends and deliverability over 7 and 30 days with inbox placement. 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_sending_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.9/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's 'Reads only' merely restates it. What it adds beyond the annotations is scope of disclosure: per-mailbox readiness including failure reasons, auth posture (SPF/DKIM/DMARC), queued sends, and two deliverability windows with inbox placement — telling the agent how much diagnostic surface it gets back. It does not mention rate limits or response size, which keeps it from a 5.

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 the resource first and the enumerated contents following, and no filler or marketing language. The field list is long and comma-chained rather than grouped, which slightly reduces scannability, but each item conveys distinct return data.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing return values — and it does so thoroughly, covering settings, per-mailbox state, authentication, queue depth, and deliverability windows. For a zero-parameter read tool whose annotations already cover safety, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The field enumeration in the description describes output, not inputs, which is appropriate here.

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 the exact resource (the account's email sending settings) and enumerates the concrete contents: on/off state, send_on_weekends, daily and per-mailbox limits, send interval, sending hours, stop-on-reply, mailbox readiness with reasons, auth records, queued sends, and 7/30-day deliverability. 'Reads only' implicitly contrasts it with the mutating sibling update_email_sending_settings, though it never names that sibling outright. An agent can tell what data it retrieves, but the read/write split is left partly to inference.

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 diagnostic/inspection call to run before changing configuration, especially given the sibling updater. There is no explicit 'use this when…' statement, no mention of prerequisites, and no named alternative. Adequate but leaves routing to inference.

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