Skip to main content
Glama

Add to list

add_to_list
Destructive

Add contacts to a list by contact_ids and/or phone_numbers (up to 1,000; numbers must already be 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": "add_to_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.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, destructive semantics, so the bar is lower. The description still adds operationally important context beyond them: the 1,000-item batch cap and the requirement that phone numbers already belong to existing contacts. It does not say what happens on duplicate membership or partially invalid input, which keeps it off a 5.

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 sentence with zero filler, front-loading the action and the input channels, with constraints in a tight parenthetical.

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?

For a three-parameter mutation with full schema coverage, no output schema, and annotations carrying the safety profile, the description supplies what an agent needs to call it correctly: accepted input channels, batch ceiling, and the pre-existing-contact prerequisite.

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 and the E.164 format. The description does add one thing the schema does not enforce: that contact_ids and/or phone_numbers must be supplied (either or both), which is real semantic value on top of a baseline-3 schema.

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 (add) and resource (contacts to a list) plus the two input channels. It is clearly distinguishable from remove_from_list and create_list, though it does not name any sibling explicitly.

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 context is implied by the shape of the operation (contacts must exist, numbers in E.164, up to 1,000), but there is no explicit when-to-use guidance or routing to alternatives such as upsert_contact for contacts that don't yet exist.

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.