Skip to main content
Glama
agentisend

agentisend

Render a template without sending it

render_template
Read-onlyIdempotent

Preview the HTML a template produces with your values and list the variables it needs. Missing or unknown variables are named with a fix instead of sending a half-filled email.

Instructions

Purpose: see exactly what a template produces with your values, and find out which variables it needs. NOT for: sending. Nothing leaves. Returns: the rendered HTML. An unknown or missing variable comes back named, with the fix, instead of shipping a half-filled 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": {
      "template_id": "<template_id>"
    },
    "name": "render_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesNoValues for the template variables.
template_idYesThe template id from list_templates.
version_numberNoA specific version. Defaults to the published one.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
renderedNoThe rendered subject and body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds real behavioral context beyond that: nothing is transmitted, output is rendered HTML, and unknown/missing variables are returned named with the fix rather than a half-filled result.

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?

Uses a tight Purpose/NOT for/Returns structure with zero filler, and each sentence is front-loaded with its most decision-relevant information.

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?

An output schema exists, yet the description still usefully previews the return (rendered HTML) and the error behavior (named variable plus fix). Combined with full schema coverage and rich annotations, nothing an agent needs to invoke it correctly is missing.

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 100%, with template_id, version_number, and values all documented in the schema, so the baseline is 3. The description only gestures at "your values" and "variables it needs" without adding format or constraint detail beyond the schema.

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?

Starts with a specific verb+resource ("see exactly what a template produces with your values") and adds a second distinct outcome ("find out which variables it needs"). This cleanly separates it from send_email and publish_template among the siblings.

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?

Provides an explicit exclusion via "NOT for: sending. Nothing leaves." which tells the agent when not to reach for it. It stops short of naming the actual alternative sibling (send_email/preflight_email), so routing is good but not fully directed.

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