Skip to main content
Glama

Coline

Extend an invite

extend_invite

Gives a pending invite seven more days.

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": "<workspace>",
      "inviteId": "<inviteId>"
    },
    "name": "extend_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesinviteId from list_members.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds the concrete mutation effect (seven more days) but leaves a meaningful ambiguity: whether repeated calls stack cumulatively (matching idempotentHint=false) or reset the window, and whether the invitee is notified.

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 zero filler, and the key fact — seven more days — is stated up front. It is efficient but so terse that structure beyond the one declarative statement is absent.

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?

This is a simple two-parameter mutation with full schema coverage, annotations, and an output schema, so most of the burden is already carried elsewhere. Still, an agent invoking a mutation that changes invite expiry would benefit from knowing the extension semantics (additive vs. reset) and any preconditions on the invite's state.

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% and both parameters carry sourcing hints ('inviteId from list_members', 'workspace slug from workspaces.list'). The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific action and outcome: extending a pending invite's lifetime by exactly seven days. The resource and effect distinguish it from invite_member and revoke_invite, though the description never names a sibling to route against.

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?

The phrase 'pending invite' implicitly scopes applicability to invites that have not yet been accepted or revoked, which is useful context. However, there is no explicit when-to-use vs. when-to-resend guidance and no mention of alternatives such as revoking and re-inviting.

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