Skip to main content
Glama
Sign In
@dropthis/mcp

@dropthis/mcp

Official
by dropthis-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List my invitations

dropthis_invitations
Read-only

List your pending workspace invitations, including invitation ID, workspace, role, status, and expiry. Requires members:read permission.

Instructions

List the workspaces you have been invited to (your own pending invitations) — each row carries the invitation id, the workspace it is for, the role you would join as, its status, and when it expires. Requires a team-scoped credential (ADR-0068: members:read). Accept one with dropthis_accept_invitation (by invitation_id here, or by the raw token from the invite email).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dropthis_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
invitationsNoThe caller's own invitations {id, workspaceId, email, role, status, expiresAt}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'List'. It adds behavioral context beyond annotations: the specific return fields (invitation id, workspace, role, status, expiry) and the required auth scope (ADR-0068: members:read). No contradiction with annotations.

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: the first states purpose and return fields, the second covers auth requirement and references the accept action. Each clause adds value with no redundancy, and the description is front-loaded with the core purpose.

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 zero-parameter read-only tool with an output schema present, the description covers purpose, scope, auth, and related next action. It is complete for its complexity.

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?

The tool has zero parameters, so schema coverage is inherently 100%. The description does not need to explain parameter semantics and does not attempt to. Baseline 4 applies for zero-parameter tools.

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?

The description uses a specific verb 'List' and resource 'workspaces you have been invited to', clarifying it lists pending invitations. It further scopes to 'your own pending invitations', distinguishing it from siblings like dropthis_members and dropthis_accept_invitation.

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?

Provides clear context (list pending invitations) and a prerequisite (team-scoped credential with members:read). Names the alternative tool dropthis_accept_invitation for acting on an invitation. However, it does not explicitly state when not to use this tool compared to other list tools, though the 'your own pending invitations' scoping reduces ambiguity.

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

Deploy Server

Other Tools