Skip to main content
Glama

Remove member or invite

share_remove

Remove a member of an artifact you own by email, or cancel that email's pending invite (owner only). Call this only when the user asks to remove someone's access. Returns { id, email, target: member|invite }; not_found when the email is neither.

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": {
      "id": "<id>",
      "email": "<email>"
    },
    "name": "share_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the owner-only authorization requirement, the return shape { id, email, target: member|invite }, and the not_found outcome when the email matches neither. There is mild tension with destructiveHint=false, since the tool revokes access, but the description does not claim reversibility or irreversibility, so this is under-disclosure rather than contradiction.

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, zero filler, with the primary action and the dual member/invite behavior front-loaded before the call gate and the return contract. Every sentence contributes information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description usefully reports the return shape and the not_found error case and states the owner-only prerequisite. The single remaining gap is the unexplained 'id' parameter, which is significant given the absent schema documentation.

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 description coverage is 0%, so the description must carry all parameter meaning. It explains the email parameter well (identifies the member or pending invite) but never mentions the required 'id' parameter at all, leaving the agent to guess whether it is an artifact id or a share record id.

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 states a specific verb and resource ('Remove a member of an artifact'), and adds the dual behavior of cancelling a pending invite, so the agent knows this tool covers two removal targets. This is clearly distinguishable from sibling invite/role tools 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?

'Call this only when the user asks to remove someone's access' gives an explicit trigger condition plus an implicit exclusion. It stops short of naming a counterpart for adjacent intents (for example changing someone's role via share_role rather than removing them), so guidance is clear but not fully comparative.

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