Skip to main content
Glama

send_invitation

Invite a prospective client to join Trainzilla under this coach, by email (confirm-gated). They receive an email with a signup link.

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": {
      "email": "<email>"
    },
    "name": "send_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
expiresInHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world action, so the safety profile is covered. The description adds real behavioral value on top: it discloses that an actual email with a signup link reaches the recipient and that a confirmation gate applies. It stops short of covering duplicate invitations, resend behavior, or rate limits.

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 tight sentences with the core action and the recipient outcome front-loaded; nothing is redundant and no filler is present.

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

Completeness3/5

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

With no output schema and a mutation that causes an outbound email, the definition should say more about what happens in preview mode versus execution and what the agent gets back. The confirm gate is flagged but the undefined expiresInHours leaves a gap an agent cannot resolve from structured fields alone.

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 only 33%: the 'confirm' parameter is documented in the schema, but 'email' and 'expiresInHours' are bare. The description partially compensates by establishing email as the delivery channel and reinforcing the confirm gate, but it never explains that expiresInHours controls signup-link lifetime, leaving one parameter entirely opaque.

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 uses a specific verb and resource — invite a prospective client to join Trainzilla 'under this coach' — and specifies the channel (email). The singular 'a prospective client' implicitly separates it from bulk siblings like send_bulk_invitations and bulk_invite_clients, though it never names the counterpart invite-response tool.

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?

The '(confirm-gated)' note tells the agent an execution gate exists, which is genuine usage context. However, there is no explicit when-to-use versus when-not-to-use guidance, no mention of when to prefer bulk invitation tools, and no note about handling already-invited prospects.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.