Skip to main content
Glama

send_report

Email a report to an allowlisted recipient, optionally including an approval ID for policy-mediated delivery.

Instructions

Envía un informe por correo a un destino de la lista blanca.

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": {
      "to": "<to>",
      "body": "<body>"
    },
    "name": "send_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
approval_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one meaningful constraint (the destination must be on the whitelist, so non-listed addresses presumably fail), but it says nothing about the approval_id gate, whether delivery failures are reported, or what side effects occur when the send succeeds.

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?

A single front-loaded sentence with no redundant wording. It is efficient, though the brevity edges toward under-specification rather than tight, information-dense concision.

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 side-effecting email tool with no annotations, a 0%-covered three-parameter schema, and an unexplained approval gate, this one-liner is too thin. An output schema does exist so return values need not be covered, but the preconditions and the approval_id workflow are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters. The description only adds meaning to 'to' (must be whitelisted); it says nothing about the format or content expectations for 'body' or, more importantly, what 'approval_id' is, how it is obtained, or whether an empty default means the send is unapproved or auto-approved.

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?

States a specific verb+resource+channel: send a report by email, restricted to a whitelisted destination. An agent can tell this is an email-delivery action rather than a generic HTTP call (http_post) or a read tool. It stops short of naming how it differs from siblings, so the distinction must be inferred.

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

Usage Guidelines3/5

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

Usage is only implied: use this to email a report to an approved address. There is no explicit when-to-use vs. when-not guidance, no mention of the http_post alternative for non-report sends, and no stated preconditions for obtaining the approval_id the schema requires.

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