Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

remove_party_phone_number_by_id

Removes a phone-number entry from a party using its row id. Find the id with get_party; the action is idempotent and reversible via add_party_phone_number.

Instructions

Remove one phone-number entry from a party by its row id. Atomic and reversible — no confirm: true gate (re-add with add_party_phone_number). Discover the id via get_party. Idempotent on retry: response is {removed: true, alreadyRemoved: false, partyId, phoneNumberId, party} on a fresh remove or {removed: true, alreadyRemoved: true, partyId, phoneNumberId} if the row was already gone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partyIdYes
phoneNumberIdYesCapsule's id for the phone-number row. Read it from get_party (each entry in phoneNumbers carries an id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / required
      Added value: +[
+  "partyId",
+  "phoneNumberId"
+]
  2. Addedv1.7.0
  3. Removedv1.6.2
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes far beyond the annotations by disclosing atomicity, reversibility, absence of a confirm gate, idempotency, and the exact response shapes for both fresh and repeated removals. This rich behavioral detail clarifies why destructiveHint is false despite the remove operation.

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 dense sentences carry all essential information: operation, behavioral traits, id discovery, and idempotency semantics. The action is front-loaded, and every clause earns its place without redundancy.

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?

Given the absence of an output schema, the description fully specifies return values for both success and already-removed scenarios. It also covers how to obtain the required id and how to revert the operation, leaving little ambiguity for an agent.

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 description adds meaning by explaining that phoneNumberId is a row id discoverable via get_party, complementing the schema's existing note. partyId is self-evident from its name and the required fields; with 50% schema coverage, the description effort is adequate.

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 ('Remove'), a precise resource ('phone-number entry'), and the targeting mechanism ('by its row id'), making the tool's scope unmistakable. This clearly differentiates it from sibling removal tools like remove_party_email_address_by_id or remove_party_address_by_id.

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 provides clear context: discover the id via get_party, and re-add with add_party_phone_number if needed. It does not explicitly contrast with sibling removal tools, but the specificity of 'phone-number entry by row id' makes the usage context unambiguous.

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