Skip to main content
Glama
Sign In

TeamMeet

by io.github.theguysaccount
OverviewDiscussionsAdmin

invite

Send the link to a running meeting to people by email — Meetful emails each one, " invited you to a Meetful", with the link. Up to 10 at a time. Or skip this and paste the returned message into wherever you talk to them.

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": "<meeting>",
      "emails": "<emails>"
    },
    "name": "invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboutNoWhat the meeting is about, in a few words.
emailsYes
meetingYesThe meeting code, like abc-defg-hij, or its link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the real side effect (Meetful sends an email to each address), the message content, the 10-recipient batch limit, and that a pasteable message is returned. It doesn't cover failure modes for invalid addresses, whether invitees need accounts, or whether sending is reversible.

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 dense sentences, front-loaded with the action and followed by the constraint and the alternative. Nothing is redundant and the fallback option is placed after the primary path where it belongs.

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 a three-parameter, no-output-schema tool, this covers action, side effect, limits, and the shape of the return value ('the returned message'). The main omission is the about parameter and any guidance on what happens to addresses beyond the tenth.

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

Parameters4/5

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

It adds meaning beyond the 67%-covered schema: the 'up to 10 at a time' cap on emails is absent from the schema, and 'running meeting' clarifies that the meeting parameter targets a live session. The about parameter is never mentioned in the description, leaving that one field to the thin schema text.

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 (send/email) and resource (the link to a running meeting), and distinguishes the action from chat-style messaging by noting the recipients get a Meetful-branded email. An agent can tell this is an outbound email invite, not a chat message or a meeting-creation call.

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?

The description gives clear usage context (inviting people by email to a running meeting, max 10 at a time) and offers an explicit alternative workflow: skip it and paste the returned message wherever you talk to them. It stops short of naming a specific sibling like send_message, so the routing is implied rather than stated.

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

All TeamMeet 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