Skip to main content
Glama

Create template

create_template
Destructive

Save a message template. Merge tags: {{first_name}}, {{name}}, {{phone}}, {{field:}}, and per-recipient variables.

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>",
      "body": "<body>"
    },
    "name": "create_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe message text, with merge tags
nameYesTemplate name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"The message text, with merge tags"
    • addedInput schema / properties / name / description
      Added value: +"Template name"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write profile is known. The description adds genuinely useful creation-time context — the supported merge-tag syntax — but says nothing about name uniqueness, whether body merge tags are validated at save time, or permissions. Given the odd destructiveHint=true on a create operation, some clarifying context would have helped.

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?

Two sentences, front-loaded with the action, with the merge-tag list packed into a single compact clause. The trailing "per-recipient variables" is slightly opaque but costs little space.

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?

The tool is simple (two required params, no nesting, no output schema to explain), so the merge-tag documentation covers the main non-obvious need. However, nothing is said about what a successful save produces (template ID) or how duplicate names are handled, leaving the create lifecycle underspecified.

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 coverage is 100%, so both name and body are already documented, and the description rightly focuses on adding the merge-tag vocabulary for body rather than restating fields. The listed tag forms are a real addition, but "per-recipient variables" is left undefined, so the value added is partial.

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?

The description opens with a specific verb+resource ("Save a message template") that matches the name unambiguously. It doesn't distinguish itself from update_template or delete_template, but the create/save semantics are clear enough for an agent to pick it out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus update_template (editing an existing template) or delete_template, and no prerequisites or constraints called out. The agent must infer from the verb alone that this is the creation path.

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.