Skip to main content
Glama
Sign In
drop2run-mcp

drop2run-mcp

Official
by Drop-to-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove someone from a site's list

remove_person
DestructiveIdempotent

Remove one email address from a site's access list, revoking invite-only access. Use it when you need to end a person's access; re-adding requires a new invitation.

Instructions

Takes one address off a site's list. On an invite-only site their access ends within a minute; putting them back is another invitation, with another email.

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": {
      "site": "<site>",
      "email": "<email>"
    },
    "name": "remove_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSubdomain or site id, from list_sites.
emailYesThe address to remove, from list_people.

Output Schema

NameRequiredDescriptionDefault
emailYesThe address removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral detail: on invite-only sites access ends within a minute, and restoration requires a fresh invitation and email — useful reversibility cost. It does not explain what happens on non-invite-only sites, leaving a gap.

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, no filler, with the core action front-loaded and the consequence trailing. Every clause carries information.

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?

Output schema exists so return values need no explanation, and annotations carry the destructive/idempotent profile. The description supplies the missing human-relevant context (timing and reversibility), making the definition sufficient to invoke correctly.

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 coverage is 100% and both parameters are documented with their source tools (list_sites, list_people). The description's 'one address off a site's list' merely echoes the schema semantics without adding syntax or format detail, 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 (remove/take off), the resource (a site's list), and the scope (one address), which cleanly separates it from invite_people and the list_* siblings. An agent can tell what it does without opening the schema.

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?

The description frames the operation's purpose (ending someone's access) and its cost ('putting them back is another invitation'), which steers the agent toward using it only when removal is intended. It stops short of an explicit when-not-to-use or a named alternative, but the context is clear.

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