Skip to main content
Glama

Send meeting invite

send_meeting_invite
DestructiveIdempotent

Sends the picker email to the invitee. Idempotent: an already-sent invite never re-sends. Errors when the meeting isn't awaiting the invitee's pick, or when it was created in shareable mode (no invitee email; share the picker_url instead). A workspace governance policy may still require_approval on this tool; that path is independent. Returns the meeting's full state.

When to use: In the same turn as propose_meeting, once the user has okayed the topic and agenda: that content go-ahead is the authorization to send, so don't ask for a separate send confirmation. On its own only when the user earlier said to hold the send and is now telling you to send it. Never without a clear human go, never on your own initiative.

Example: Okay, send Sara that invite now.

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": {
      "meeting_id": "<meeting_id>"
    },
    "name": "send_meeting_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYesThe meeting's id, from propose_meeting or search_records.

Output Schema

NameRequiredDescriptionDefault
sentNo
slotsNo
meetingNo
picker_urlNo
already_sentNo
email_skippedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / properties / meeting_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed6 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / meeting / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / meeting / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / slots / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / slots / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it names the exact error conditions (meeting not awaiting the invitee's pick, shareable-mode meetings) and the correct remediation (share picker_url), and discloses that a governance approval path can block the call independently. The idempotency claim is consistent with idempotentHint=true and the external-effect nature is consistent with openWorldHint/destructiveHint; no contradiction.

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?

Behavior and failure modes are front-loaded, then usage, then a short example — a sound order. Slightly padded by near-duplication between 'don't ask for a separate send confirmation' and 'Never without a clear human go,' which cost a point.

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

Completeness5/5

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

An output schema exists, yet the description still orients the agent ('Returns the meeting's full state'). With one fully-specified parameter, rich annotations, and explicit failure handling, nothing needed to call this correctly is absent.

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 100% and the sole parameter is documented as a uuid sourced 'from propose_meeting or search_records.' The description does not restate or add syntax for meeting_id, so this sits at the baseline where the schema does the work.

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?

States a specific verb and resource ('Sends the picker email to the invitee'), not a restatement of the name. It also scopes what it is not: it errors in shareable mode where share/picker_url is the answer, which separates it from the invite-adjacent siblings.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('in the same turn as propose_meeting, once the user has okayed the topic and agenda'), a narrow standalone case, and hard when-nots ('Never without a clear human go, never on your own initiative'). It even resolves the authorization ambiguity by saying the content go-ahead doubles as send authorization.

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.

Resources