Skip to main content
Glama
rhyeal

wealthbox-mcp

by rhyeal

wealthbox.households.deleteMember

Delete a member from a household in Wealthbox CRM by providing the household ID and the member ID. Use this to manage household relationships.

Instructions

Delete member from a household

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
household_idYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Delete member from a household,' which is nearly identical to the tool name and does not explain irreversibility, side effects, or any required permissions. The destructive nature is implied by 'delete' but not elaborated.

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?

A single short sentence that is direct and front-loaded. Every word contributes to the core meaning, and there is no waste or redundant information.

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

Completeness2/5

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

Given the simplicity of a two-parameter delete, the description is still incomplete. It lacks parameter semantics, usage guidance, and any behavioral context. The lack of annotations and output schema further increases the burden, which the description does not meet.

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% and the description adds no parameter details. While the parameter names 'household_id' and 'id' offer some hint, 'id' is ambiguous (member ID? contact ID?) and the description does not clarify. It fails to compensate for the lack of schema descriptions.

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 ('Delete') with a clear resource ('member') and location ('household'), which directly distinguishes it from sibling tools like wealthbox.households.addMember. While terse, it fully conveys the tool's primary action.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. It neither mentions prerequisites, exclusions, nor related operations. The description simply states the action without contextualizing it among the sibling tools.

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/rhyeal/wealthbox-mcp'

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