Skip to main content
Glama
Sign In
MCP VTEX Server

MCP VTEX Server

by leosepulveda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vtex_send_email

Send transactional emails using predefined templates with dynamic data for VTEX e-commerce operations.

Instructions

Send an email using template

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": {
      "templateName": "<templateName>",
      "jsonData": "<jsonData>"
    },
    "name": "vtex_send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateNameYesTemplate name
jsonDataYesData for template variables
providerNameNoEmail provider name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('Send') but doesn't disclose critical traits like authentication needs, rate limits, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action, though it could be more specific. While concise, it risks under-specification given the tool's complexity.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral expectations, error cases, or return values, leaving significant gaps for an agent to invoke it correctly. The high schema coverage doesn't compensate for missing operational context.

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 parameters are documented in the schema. The description adds no additional meaning beyond implying template usage, which is already covered by the 'templateName' parameter. Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't compensate with extra context like template variable examples or provider specifics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Send an email using template' clearly states the verb ('Send') and resource ('email'), but it's vague about scope and doesn't distinguish from siblings. While it mentions 'using template', it doesn't specify what kind of email (e.g., transactional, marketing) or how it relates to sibling tools like 'vtex_create_email_template' or 'vtex_get_email_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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing an existing template), exclusions, or how it differs from other email-related operations in the sibling list, leaving the agent with no context for selection.

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