Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Create Template Draft

create_template_draft

Create a draft of a new template. The draft can be edited, previewed, and saved as a template. 'template_format' documents the template format, with examples.

Every sender identity, recipient and recipient group the template references must already exist; a reference to one that does not fails validation. Sender identities, recipients and groups are listed by 'list_sender_identities', 'list_recipients' and 'list_groups', and created by 'create_sender_identity', 'create_recipients' and 'create_group'.

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": {
      "Name": "<Name>",
      "Template": "<Template>"
    },
    "name": "create_template_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
NameYesNew template name. Must be unique.
TemplateYesEmail template in GoodSender format. Documentation: 'template_format' tool.

Output Schema

NameRequiredDescriptionDefault
ResultYesResult of the operation.
TemplateTokenYesTemplate token accepted by 'render_template_preview', 'edit_template', 'get_template_content' and 'save_template'.
TemplateDataSchemaYesData schema inferred from the template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / TemplateToken / description
      Previous value: -"Template token accepted by 'render_template_preview', 'modify_template' and 'save_template'."New value: +"Template token accepted by 'render_template_preview', 'edit_template', 'get_template_content' and 'save_template'."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare a non-read-only, non-idempotent, non-destructive mutation. The description adds useful behavioral detail beyond annotations: the draft is editable/previewable/saveable, and validation fails when referenced sender identities, recipients, or groups do not already exist.

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?

The definition is front-loaded with the core action and lifecycle, then follows with format documentation and validation prerequisites. It is slightly repetitive in pointing to 'template_format', which the schema also mentions, but overall it is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple two-parameter schema, existing annotations, and an output schema, the description covers what the agent needs: what the tool creates, what can be done with the draft, where format documentation lives, and which reference entities must already exist. No critical behavioral gap is left for an agent invoking this tool.

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?

Schema coverage is 100%, so the schema already documents both parameters, including the uniqueness requirement for 'Name' and the GoodSender format for 'Template'. The description adds meaning by pointing to 'template_format' for examples and by explaining the reference-validation constraint on template content.

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 states a specific verb and resource: 'Create a draft of a new template.' It also clarifies the draft lifecycle ('edited, previewed, and saved as a template'), so the agent can distinguish this from immediate template creation or editing tools.

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 gives clear usage context: create a draft that can later be previewed and saved. It also provides prerequisite guidance for references, naming the list and create tools for sender identities, recipients, and groups. It does not explicitly contrast this with siblings like 'save_template' or 'edit_template', which keeps it from a 5.

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

All GoodSender 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