Skip to main content
Glama
ictdialer-mcp

ictdialer-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ICTDIALER_BASE_URLYesServer base URL, without the /rest suffix, e.g. https://your-ictdialer
ICTDIALER_PASSWORDYesPassword for that account
ICTDIALER_USERNAMEYesAPI account username
ICTDIALER_TIMEOUT_MSNoPer-request timeout30000
ICTDIALER_TLS_INSECURENoSkip TLS verification — self-signed test servers onlyfalse
ICTDIALER_MCP_ALLOW_WRITENoUnlock start/stop campaign (see Safety)false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ictdialer_list_campaignsA

List the outbound campaigns on the ICTDialer server (id and name of each). Start here to find a campaign id.

ictdialer_campaign_statusA

Live status of a campaign by id (for example running or stopped). Poll this while a campaign runs.

ictdialer_campaign_summaryB

Totals for a campaign: answered, failed, human vs machine and so on. Optionally scope to one agent/user id.

ictdialer_campaign_resultB

Per-call results for a campaign (contact, response, answering-machine detection, DNC), optionally filtered by call status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct slice of campaign data: live status, aggregate totals, per-call rows, and the campaign list. The only mild overlap is status vs. summary, both 'campaign-level overview' tools, but descriptions differentiate live state from aggregate metrics well.

Naming Consistency4/5

All names are snake_case and share the ictdialer_ prefix, with campaign-noun suffixes (status, summary, result). The outlier is ictdialer_list_campaigns, which uses verb_noun while the others use noun_resource ordering, a minor deviation.

Tool Count3/5

Four tools is thin for a dialer server; the surface is entirely read-only monitoring with no control operations. Each tool earns its place, but the scope feels under-built rather than well-scoped.

Completeness2/5

Only observation is covered; there is no way to create, start, stop, pause, or edit a campaign, nor any contact/list management. An agent can inspect campaigns but hits a dead end for any lifecycle action.

Maintenance

ActivityMaintained
ResponsivenessNo issues