Skip to main content
Glama
Sign In

EmailFig

by com.emailfig
OverviewDiscussionsAdmin

Send test email

send_test_email
Destructive

Emails a test of a draft campaign to the connected person's own address, with sample values for merge tags. It goes only to that address and only for a draft; it never sends the campaign. A draft written as blocks can be tested once someone opens it in EmailFig, which builds its 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": {
      "id": "<id>"
    },
    "name": "send_test_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe draft's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description explains why the side effect is bounded — the email goes solely to the account owner's address and the campaign itself is never dispatched. It also surfaces a real failure precondition (blocks drafts must be opened in EmailFig first), which is genuine context beyond the annotations. It stops short of covering rate limits or failure behavior.

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?

Three short sentences, front-loaded with the action, then the scope limits, then the precondition. Nothing is padding, though the closing clause 'builds its email' is slightly vague about which email it refers to.

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?

For a one-parameter, no-output-schema tool with annotations already carrying the safety profile, the description covers what an agent needs: who receives it, what state the draft must be in, and that the campaign is not sent. Minor gaps remain around error behavior when the precondition is unmet.

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?

There is only one parameter and schema coverage is 100%, with the schema already stating 'The draft's id.' The description implies the draft must exist and, in the blocks case, be opened first, but adds no format or sourcing detail beyond the schema. Baseline 3 applies.

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?

The description names a specific verb and resource ('Emails a test of a draft campaign') and immediately delimits it against the thing an agent might confuse it with: 'it never sends the campaign.' That contrast with real campaign sending is exactly the disambiguation an agent needs.

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?

It states the operating envelope explicitly: only to the connected person's own address, only for a draft, and blocks-based drafts are testable only after being opened in EmailFig. No named alternative is offered, but the when-it-works preconditions are clear.

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

All EmailFig toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources