Skip to main content
Glama

get_welcome_email

Read-onlyIdempotent

Read the saved welcome email draft and the draft and sender settings revisions used by the active automation.

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_welcome_email"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the read includes draft and sender-settings revision history tied to the active automation, which is genuinely useful context, but it says nothing about how much history is returned, ordering, or whether a missing draft yields an empty result or an error.

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?

A single sentence with no filler, which is appropriate for a zero-argument read. The one weakness is the stacked phrasing 'the draft and sender settings revisions', which forces a re-read to parse what two things are being returned.

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?

With no output schema, the description carries the burden of explaining what comes back, and it only gestures at 'draft and sender settings revisions' without indicating structure or whether multiple revisions are returned. For a simple read-only tool this is close to sufficient, but the return shape remains ambiguous.

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 and the schema is an empty closed object, so there is no parameter meaning to explain. Baseline for a no-parameter tool applies; the description correctly implies no inputs are needed by describing a plain read of the active configuration.

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 ('Read') and resource ('the saved welcome email draft'), and extends it to related revision data. It is distinguishable from the sibling save_welcome_email_draft by the read framing, though the phrase 'the draft and sender settings revisions used by the active automation' is convoluted enough that the exact scope of what is returned is not immediately clear.

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 how you inspect the current welcome email state before editing or sending. There is no explicit when-to-use statement, no mention of alternatives such as save_welcome_email_draft or get_email_settings, and no preconditions given.

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