Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Check campaign step

check_campaign_item
Read-onlyIdempotent

Reads back a customer's campaign step text, flags typos, vague or missing parts, asks up to two questions, and suggests cleaned wording without saving anything.

Instructions

Reads back what a customer wrote for one campaign step (targeting, signals or offering), using the other steps as context when given. Returns reading (what was understood), issues (typos, vague or missing parts), questions (at most two worth answering), suggested_text (a cleaned wording, empty when the text is fine) and confident. Reads only; nothing is saved.

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": {
      "field": "<field>",
      "text": "<text>"
    },
    "name": "check_campaign_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat the customer wrote for that box, verbatim.
fieldYesWhich box to read back: targeting, offering or signals.
offeringNo
targetingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with 'Reads only; nothing is saved.' It goes further by describing the return payload in detail (reading, issues, at most two questions, suggested_text empty when the text is fine, confident), which matters because there is no output schema.

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?

One front-loaded sentence states the action and scope, followed by a compact enumeration of the return fields; nothing is filler. The return-value list is long but each item carries distinct information.

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?

With no output schema and a four-parameter input, the description covers both what the tool reads and what it returns, including an edge case (suggested_text empty when the text is fine). Minor gaps remain on length limits and how outputs shift when context steps are omitted.

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 description coverage is 50%, so several parameters are documented structurally already. The description adds real meaning only for the optional context parameters ('using the other steps as context when given') and otherwise restates the field/text concepts, leaving the interaction between the required text and optional step context underexplained.

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 definition names a specific verb and resource ('Reads back what a customer wrote for one campaign step') and enumerates the three possible steps (targeting, signals, offering). It clearly reads as a review/feedback operation rather than a campaign mutation, though it never names a sibling to contrast with.

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?

The clause 'using the other steps as context when given' implies that passing the optional targeting/offering values improves the reading, and 'Reads only; nothing is saved' signals a pre-save review use case. However, there is no explicit statement of when to call this versus saving the item directly, nor any stated preconditions.

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