Skip to main content
Glama

save_welcome_email_draft

Save the welcome email draft for owner review. Use revision 0 for a new draft or the current revision from get_welcome_email.

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": {
      "revision": "<revision>",
      "value": "<value>"
    },
    "name": "save_welcome_email_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description reinforces the review-gated nature ('for owner review'). However, it doesn't say what an out-of-date revision does (conflict/overwrite), whether saving overwrites the whole draft or merges, or any validation failures — important for a non-idempotent write with a revision guard.

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?

Two short sentences, zero filler: the action first, then the revision rule. Every sentence earns its place.

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 two-parameter tool with no output schema, the description covers the action and the revision semantics adequately. It falls short on the deeply nested draft payload and on the result of a successful save (e.g., returned revision for the next call), which matter given the revision-based workflow.

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 0%, but the description does explain the tricky parameter: what value to pass for `revision` and where to get it. It adds nothing about the large nested `value` object (name, subject, previewText, body, serviceBlocks), whose constraints are only encoded in JSON Schema keywords rather than human-readable descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Save the welcome email draft') plus the intent ('for owner review'), which distinguishes it from create/send siblings such as get_welcome_email and send_appointment_change_email.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit revision rule — 'Use revision 0 for a new draft or the current revision from get_welcome_email' — which routes the agent to the right companion read tool for updates. It does not state when not to use this tool (e.g., vs save_email_campaign_draft), but the context is clear enough for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources