Skip to main content
Glama
Sign In
aspa-mcp

aspa-mcp

by octos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Enviar template

aspa_send_template
Destructive

Sends an approved WhatsApp template outside the 24-hour window after explicit user approval, enabling customer or team messaging when standard replies are restricted.

Instructions

Send an approved WhatsApp template (works outside the 24h window). This is a real action visible to the customer or the team. Only call it after the user explicitly approved this exact action in the conversation.

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": {
      "contact": "<contact>",
      "template": "<template>"
    },
    "name": "aspa_send_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoIndex from aspa_list_conversations, only to tell apart contacts with the same name.
contactYesContact name exactly as listed. Required for every action that changes a conversation.
templateYesTemplate name from aspa_list_templates.
variablesNoValues for the template variables, in order.
conversation_idNoconversation_id returned by aspa_read_conversation. When given, the action is refused if the open conversation is a different one.
confirm_duplicateNoOnly true when the user explicitly wants to repeat the same message sent less than 2 minutes ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.2/5.0
Behavior4/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/irreversible profile is known. The description adds real behavioral context beyond that: the message is visibly delivered to the customer or team, it bypasses the 24h window, and it requires explicit prior approval. It does not cover delivery failure or duplicate handling, which the schema mentions instead.

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?

Two short sentences, both front-loaded with the highest-value information: what it sends and the approval prerequisite. No filler wording.

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

Completeness4/5

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

For a destructive, open-world send tool with annotations and a fully documented 6-parameter schema, the definition covers the essentials: what it sends, its visibility, and the approval gate. It leaves the outcome of the call (delivery confirmation, error on refused conversation_id) unstated, though the schema partly compensates for the latter.

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%, so every parameter including conversation_id and confirm_duplicate is already documented. The description adds only the qualifier that the template must be 'approved', which the schema does not state, but otherwise repeats schema-level meaning. Baseline 3 is appropriate.

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 gives a specific verb and resource ('Send an approved WhatsApp template') and adds the distinguishing scope 'works outside the 24h window', which separates it from aspa_send_message and aspa_send_attachment without opening either schema.

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 states a hard precondition: only call after the user explicitly approved this exact action in the conversation. That is a clear usage gate. It stops short of naming alternatives (e.g., free-form reply inside the 24h window), which keeps it at 4 rather than 5.

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

Deploy Server

Other Tools