jotae-mcp

create_template

Create a new WhatsApp or email template with customizable body, subject, and sender name. Supports variables like {{nome}} and {{evento}} for personalization.

Instructions

Cria um novo template de WhatsApp ou e-mail com conteúdo.

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

Input Schema

Name	Required	Description
`body`	Yes	Corpo da mensagem. Use {{nome}}, {{evento}} como variáveis.
`name`	Yes	Nome do template
`channel`	Yes	Canal do template
`subject`	No	Assunto (só e-mail)
`folder_id`	No	ID da pasta (use list_folders ou create_folder)
`media_url`	No	URL de mídia opcional (WhatsApp)
`media_type`	No	Tipo de mídia (WhatsApp)
`destination`	No	Destino WhatsApp (padrão: individual)
`sender_name`	No	Nome do remetente (só e-mail)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 27, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'creates', implying mutation, but does not explain side effects (e.g., validation, duplicate handling, approval requirements) or any constraints beyond what the schema indicates.

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?

The description is a single sentence with no wasted words. It is maximally concise while still communicating the core function. For a tool with 9 parameters, the brevity is acceptable because the schema provides parameter details.

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

Completeness2/5

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

Despite having 9 parameters and no output schema, the description does not explain return values, side effects, or how this tool fits into the larger workflow (e.g., differentiating from update_template). It covers only the basic function, leaving significant gaps for an agent.

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 the baseline is 3. The description does not add any parameter-specific information beyond what the schema already provides. It does not mention parameters like body, folder_id, etc., so it adds no extra semantic value.

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 clearly states that the tool creates a new WhatsApp or email template ('Cria um novo template de WhatsApp ou e-mail com conteúdo'). It uses a specific verb ('cria') and resource ('template'), and the mention of channels distinguishes it from siblings like list_templates or update_template.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., update_template), nor does it specify prerequisites or scenarios where this tool is appropriate. It simply states what it does.

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