get_email_templateGet a single email template by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Template ID (from list_email_templates) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The template — id, name, subject, message, button_text and button_top. | |
| success | Yes | True when the call succeeded. A failure comes back as an error result instead. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": {},
+ "description": "The template — id, name, subject, message, button_text and button_top.",
+ "type": "object"
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond fetching a single template by ID. It doesn't mention return format, error behavior, or any side effects, but for a simple read operation with annotations covering safety, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with zero waste. The description is front-loaded with the verb and resource, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-resource read tool with a fully documented schema, an output schema, and annotations covering safety, the description is complete enough. It could mention that the ID comes from list_email_templates, but that's already in the schema. Nothing critical is missing for an agent to call this correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the only parameter 'id' is described as 'Template ID (from list_email_templates)'. The description adds no additional parameter meaning beyond what the schema already provides. Baseline 3 is appropriate when the schema fully documents the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Get a single email template by ID.' It is unambiguous about what the tool does. However, it doesn't explicitly distinguish itself from siblings like get_template or list_email_templates, though the resource 'email template' is specific enough to avoid major confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: call this when you need a single email template by ID. It doesn't explicitly state when to use alternatives like list_email_templates or get_template, but the context of 'email template' and the single-ID parameter make the intended use reasonably clear. No exclusions or alternative routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.