Skip to main content
Glama

Remove from list

remove_from_list
DestructiveIdempotent

Remove contacts from a list (they stay contacts).

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>"
    },
    "name": "remove_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesList id
contact_idsNoContact ids
phone_numbersNoPhone numbers in E.164, of existing contacts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / contact_ids / description
      Added value: +"Contact ids"
    • addedInput schema / properties / phone_numbers / description
      Added value: +"Phone numbers in E.164, of existing contacts"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds one genuinely useful fact beyond that — contacts are preserved, only list membership is destroyed — but says nothing about behavior when an id isn't in the list, partial failures, or batch size limits.

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 with the key side-effect clarification attached up front. Nothing wasted, nothing buried.

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

Completeness3/5

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

For a three-parameter mutation with no output schema, the description is minimally sufficient but thin. It doesn't cover the id-vs-phone-number selection alternatives, error behavior for contacts not on the list, or any limit on batch size.

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%, so the schema already documents all three parameters, which sets the baseline at 3. The description adds no parameter detail, and notably does not explain that contact_ids and phone_numbers are alternative ways to select the same contacts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove contacts from a list') and the parenthetical 'they stay contacts' implicitly contrasts it with the destructive delete_contact sibling. It never names add_to_list or delete_list as alternatives, so differentiation is left partly to inference.

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

Usage Guidelines3/5

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

Usage is implied by the name and the clarification that membership is removed but the contact record survives. There is no explicit 'use this when / not when', no mention of how this relates to delete_contact or update_list.

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.