Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Ask the Email Agent

ask_email_agent
Read-only

Answers questions about your list or email agent using saved facts and returns a concise reply without reading threads or triggering email, list changes, or research.

Instructions

Answers a question about the user's list or Email Agent from saved facts, in the Email Agent's concise reply style, and returns that message. It does not read earlier email threads. Reads only: no email, list change or research is triggered.

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": {
      "question": "<question>"
    },
    "name": "ask_email_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes
config_idNo
campaign_idNo

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?

Beyond the annotations, the description discloses that it answers from saved facts rather than live threads, replies in the Email Agent's concise style, and triggers no email, list change, or research — the last point matters because sibling tools like create_research_request do trigger research. The 'Returns that message' clause conveys the return shape despite the missing output schema. It doesn't explain why the call is non-idempotent, which the annotations flag.

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 core action, followed by two limiting clauses. Nothing is redundant and nothing pads the definition.

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?

The read-only, no-side-effects profile is adequately covered, but a three-parameter tool with zero schema descriptions and no output schema needs the description to explain the config/campaign scoping and question constraints, and it doesn't. An agent can call it with just a question but cannot use the optional parameters confidently.

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 the description says nothing about what question accepts (length, whether it must be answerable from saved facts) or what config_id and campaign_id scope. Only a vague link between 'about the user's list or Email Agent' and the question parameter is present, so two of three parameters are undocumented anywhere.

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 verb and resource: it answers a question about the user's list or Email Agent from saved facts, and explicitly says it does not read earlier email threads. That negation separates it from thread-reading siblings, though it never names a concrete alternative tool such as get_email_agent_status or deep_search.

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 infers it should call this for a single self-contained question rather than for reading thread history. There is no explicit when-to-use versus when-to-use-a-sibling routing, and no guidance on how config_id or campaign_id affect which context the answer draws from.

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