Skip to main content
Glama
Sign In

VibeAdmin

by solutions.easy-admin
OverviewDiscussionsAdmin

Send an email to one user

send_email
Destructive

Send ONE email to ONE user right now (cannot be undone). Only call after the person you are helping has approved the exact subject and message.

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": {
      "user_id": "<user_id>",
      "subject": "<subject>",
      "message": "<message>",
      "confirm": "<confirm>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the sender has approved this exact email.
messageYesPlain text. Paragraphs separated by blank lines.
subjectYes
user_idYesThe user's id in your app (preferred) or the VibeAdmin id from list_users.
categoryNotransactional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description earns credit for the extra operational constraint not present in structured fields: a human-approval gate tied to the exact subject and message. 'Cannot be undone' restates destructiveHint rather than adding to it, and delivery latency, failure behavior, and rate limits go unmentioned.

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, zero filler. The irreversible nature and the single-recipient scope are front-loaded before the approval precondition, which is exactly the order an agent needs.

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 an irreversible, outward-facing send with no output schema, the description covers the essentials: one recipient, immediate, irreversible, human approval required. It is slightly incomplete on the `category` parameter's implications and on what the caller gets back or what happens on delivery failure.

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 60%, so the schema already documents user_id, confirm, and message format. The description reinforces the approval semantics of `confirm`, but it says nothing about `category` — the one enum parameter — leaving the agent unable to judge the consequences of choosing marketing versus transactional.

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 gives a specific verb and resource ('Send ONE email to ONE user right now') and constrains scope with the capitalized ONE, which implicitly separates it from the batch/broadcast and drafting siblings such as create_email_draft. It stops short of naming that alternative outright, so the differentiation is inferred rather than stated.

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 provides a clear, mandatory precondition: only call after 'the person you are helping has approved the exact subject and message.' That is stronger than generic context, but it offers no guidance on what to do instead when no approval exists (e.g., use create_email_draft), nor on which sibling handles multi-recipient sends.

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

All VibeAdmin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources