Skip to main content
Glama

Invite a teammate

invite_teammate

Invite someone to the workspace by email; they get a sign-in link that lands on the join page. Roles: rep, manager, admin (only admins invite admins).

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": "invite_teammate"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
emailYesTheir email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description only needed to add context. It does: it discloses that an external email with a sign-in link is dispatched and that an admin-only constraint governs admin-role invitations — both facts absent from the annotations.

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 the invitation mechanism first and the role constraints second — every clause carries information. The role enumeration mildly duplicates the schema enum, keeping it from a 5.

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?

For a two-parameter mutation with no output schema, the description covers side effects and permissions well. But role is optional in the schema and the description never says what happens if it is omitted (default role, or invite with no role), which is a meaningful gap for an agent deciding what to send.

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?

Schema coverage is only 50%, with the role parameter lacking any schema description, so the description carries real weight here. It enumerates the valid roles and adds the non-obvious authorization rule (only admins may invite admins), which the enum alone cannot convey; the email parameter still gets no format or normalization detail.

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 gives a specific verb and resource ("Invite someone to the workspace by email") plus the observable outcome (a sign-in link landing on the join page), which is far more informative than the title alone. It does not, however, differentiate itself from plausible siblings such as hire_crew or bullpen_signup, leaving the agent to infer which invitation path applies.

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 context is implied rather than stated — the tool is for adding a teammate to the current workspace, and the parenthetical "only admins invite admins" supplies a genuine permission precondition. There is no explicit when-not guidance or routing to alternatives like hire_crew, so the agent must guess at the boundary.

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.