Skip to main content
Glama

delete_member

Remove a member from the club. Use caution as this action is often irreversible; consider canceling membership as an alternative.

Instructions

Remove a member from the club. Use with caution - often irreversible.

Use when: "delete member 12345". Consider cancelling the membership instead - cancellation preserves the history while removing billing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
member_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description highlights the key behavioral trait of irreversibility ('often irreversible'). However, the qualifier 'often' introduces slight ambiguity. With no annotations, the description adequately conveys the main risk but could be more precise.

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 sentences with no redundancy. Front-loads purpose, then caution, then alternative. Every sentence adds value.

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?

Given the tool's simplicity (1 parameter, deletion action), the description covers purpose, caution, and alternative. However, it lacks details on what exactly is deleted (e.g., associated data) and the output schema is available but not described. Still sufficient for an agent to use 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 description coverage is 0%, so the description must compensate. It provides an example usage ('delete member 12345') which clarifies the member_id parameter, but no explicit description of the parameter's source or format. For a single self-explanatory parameter, this is adequate but minimal.

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 clearly states 'Remove a member from the club' with a specific verb and resource. It distinguishes from siblings like cancel_membership by indicating the alternative. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises caution due to irreversibility and suggests an alternative: cancel_membership. This provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sanjibani/courtreserve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server