Skip to main content
Glama

contact_leads

Destructive

Call or text a LIST of leads in one go (real calls / real SMS, billed). channel=call queues an outbound call to each lead; channel=sms sends each lead a message (message required unless sendMode=agent). leads are lead objects from leads_read (they must carry a phone, e.g. userPhone). Max 500 per call. Confirm the audience with the user first. For scheduled, throttled dialing use a campaign (campaigns_write).

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": {
      "channel": "<channel>",
      "agentId": "<agentId>",
      "leads": "<leads>"
    },
    "name": "contact_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoFor channel=sms: specific sender number.
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
leadsYes
agentIdYes
channelYes
messageNoFor channel=sms.
optionsNo
sendModeNoFor channel=sms.
campaignIdNo
contactMethodsPriorityNoLead fields to read the phone from, in order. Default ["userPhone", "phone", "userID"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds context the annotations don't carry: real traffic that is billed, a hard cap of 500 leads per call, and a required human confirmation of the audience before firing. The annotations already declare destructiveHint=true and openWorldHint=true, so the remaining gap is minor — it doesn't say what happens on partial failure (e.g., some leads lacking a phone) or whether a call can be cancelled.

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?

Four dense sentences, front-loaded with the verb-resource and the cost warning; every clause (billing, per-channel behavior, max 500, confirm audience, campaign alternative) carries information an agent needs before invoking.

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?

For a 10-parameter, nested-object, mutation-style tool with no output schema, the description covers the risk profile, batch limit, input provenance and the main routing decision. It is slightly thin on the response shape (per-lead results vs. aggregate) and on what agentId/options do, but nothing required to call it correctly is missing.

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?

With only 50% schema coverage, the description compensates by explaining channel semantics, the message/sendMode interaction, and that leads must be lead objects from leads_read carrying a phone such as userPhone. It leaves agentId, options, campaignId and the contactMethodsPriority fallback chain undocumented, though the last of these is described in the schema itself.

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?

States a specific verb (call or text) and resource (a LIST of leads) plus the blast-radius qualifier 'in one go', with real calls/SMS and billing called out. An agent can distinguish it from send_sms (single message) and start_outbound_call (single call) without opening the schema.

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 routes per channel ('channel=call queues an outbound call to each lead; channel=sms sends each lead a message'), states the message requirement gap (required unless sendMode=agent), and names the alternative for scheduled/throttled dialing ('use a campaign (campaigns_write)'). It also gives a prerequisite action: confirm the audience with the user first.

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.

Resources