Skip to main content
Glama

Resend an invitation

company_invite_resend

Sends a pending invitation e-mail again and extends its expiry. Owners and admins (admins only for member or viewer invitations). At most once a minute and 5 times per invitation. No confirmation needed; the invitation link is not shown here.

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": {
      "company": "<company>",
      "invitation": "<invitation>"
    },
    "name": "company_invite_resend"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
invitationYesInvitation ref (IV-XXXXXXXX) from company_invitations_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent); the description adds real behavioral substance beyond that: the expiry is extended as a side effect, rate limits of 1/minute and 5 per invitation apply, and no confirmation step occurs. It also pre-empts an output question by saying the invitation link is not returned here.

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?

Three short sentences, front-loaded with the action and its effect, then permissions, then limits. Every clause carries information an agent needs before calling.

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?

For a two-parameter mutation with a fully documented schema and no output schema, the definition covers effect, authorization, throttling, and absence of a returned link. Nothing material is missing for correct invocation.

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 description coverage is 100%, with both company and invitation refs patterned and documented including their source tools. The description adds no further parameter meaning, so 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: re-sends a pending invitation e-mail and extends its expiry. The words "pending" and "again" separate it from company_invite_create, and the expiry extension distinguishes it from a plain read.

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?

Gives concrete preconditions: caller must be owner or admin, and admins only for member/viewer invitations. It also sets throttling context (once a minute, five per invitation). It stops short of naming explicit alternatives such as revoke or create for different intents, so a 4 rather than a 5.

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