Skip to main content
Glama

Resend an invitation

resend_invite

Resend a workspace invitation email. Workspace owners only.

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": {
      "workspace_id": "<workspace_id>",
      "invite_id": "<invite_id>"
    },
    "name": "resend_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_idYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The description adds two useful facts beyond annotations: the operation sends an email (matching openWorldHint) and requires workspace-owner authorization. It does not address the non-idempotent nature implied by idempotentHint=false, i.e. whether repeated calls send duplicate emails or invalidate the previous invite token.

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 sentences, zero filler, with the core action front-loaded and the permission constraint immediately following. Nothing could be cut without losing information.

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 simple two-parameter mutation with annotations covering the safety profile, the description covers the action and the auth gate. It is still incomplete on invite_id sourcing and on what happens to the prior invitation when a resend occurs, which matters for an email-sending side effect.

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

Parameters2/5

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

Schema coverage is only 50%: workspace_id is documented as coming from whoami, but invite_id has no description in either the schema or the tool description. The description says nothing about how to obtain an invite_id or whether a stale/revoked invite id is acceptable, so it fails to compensate for the coverage gap.

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?

"Resend a workspace invitation email" pairs a specific verb with a specific resource and is trivially distinguishable from invite_member or revoke_invite. It stops short of explicit sibling routing, but the action is unambiguous.

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?

"Workspace owners only" gives a real eligibility prerequisite that an agent must check before calling. However, there is no guidance on when to resend versus re-inviting via invite_member, or what to do if an invitation expired versus was never delivered.

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