Capable

Send meeting invite

send_meeting_invite

DestructiveIdempotent

Sends the picker email to the invitee. Normally called in the SAME turn as propose_meeting: the user's okay on the topic and agenda IS the authorization to send, so don't ask for a separate send confirmation. Call it on its own only when the user earlier said to hold the send and now says to send. Never send without a clear human go, and never on your own initiative (a workspace require_approval policy on this tool is independent and untouched). Idempotent: a sent invite never re-sends. Errors clearly when the meeting isn't awaiting the invitee's pick or was created in shareable mode (no invitee email — share the picker_url instead). Returns the meeting's full state.

When to use: Right after propose_meeting in the same turn — the user's okay on topic and agenda is the authorization, so don't ask twice. Wait only if the user said to hold the send. Sends directly, never on the model's own initiative; idempotent.

Example: Okay, send Sara that invite now.

Input Schema

Name	Required	Description	Default
`meeting_id`	Yes	The meeting's id, from propose_meeting or search_records.

Output Schema

Name	Required	Description	Default
`sent`	No
`slots`	No
`meeting`	No
`picker_url`	No
`already_sent`	No
`email_skipped`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed1 schema field changedOct 20, 2026

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)$"

Changed6 schema fields changedOct 19, 2026
- 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"
-}
```
First observedOct 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by naming the error conditions (meeting not awaiting the invitee's pick, shareable mode with no invitee email and the picker_url fallback), stating that the workspace require_approval policy is independent and untouched, and confirming the return of full meeting state. Idempotency is reinforced with concrete behavior rather than just repeating the hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The 'When to use' block restates the opening paragraph almost verbatim ('don't ask twice' / 'don't ask for a separate send confirmation'; 'never on the model's own initiative' appears twice). The core guidance is front-loaded and valuable, but a quarter of the text is redundant restatement.

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 so return values need not be detailed, and the description still notes the full-state return. For a single-parameter, idempotent mutation tool, the authorization model, error paths, and sibling sequencing are all covered.

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 schema already documents meeting_id's origin (propose_meeting or search_records). The description adds no format, constraint, or sourcing detail beyond that, so the baseline 3 applies.

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') and immediately distinguishes itself from the adjacent sibling propose_meeting by describing the two-step flow. An agent can tell what this does without opening the schema.

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?

Explicit when-to-use ('Right after propose_meeting in the same turn'), when-not ('never on your own initiative'), the authorization model ('the user's okay on the topic and agenda IS the authorization'), and the one exception for a held send. Alternatives and conditions are fully spelled out.

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

All Capable tools Inspect

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

Need Help?