Skip to main content
Glama
SSIG-IT

3CX MCP Server

by SSIG-IT

get_call_history

Retrieve past call records with start time, caller/callee details, duration, and answered status. Filter by date, missed calls, extension, or queue to analyze call activity.

Instructions

Use this for ANY question about past calls: 'show today's calls', 'missed calls today', 'recent calls for extension 101', 'calls to queue 802 yesterday'. Returns newest calls first. Each record: StartTime, SourceDisplayName, SourceCallerId, DestinationDisplayName, DestinationCallerId, Answered (true/false), TalkingDuration, Direction, Status, Reason. Set missedOnly=true for missed/unanswered calls. Handles timezone-aware 'today' filtering automatically. Requires System Owner role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoTime window: 'today' (default), 'last_24_hours', or 'all_recent' (last 3 days)today
missedOnlyNoSet true for missed/unanswered calls only (checks both Answered=false and Status='Unanswered')
dateNoExplicit date in YYYY-MM-DD format, e.g. '2026-03-17' for yesterday
timezoneNoIANA timezone, e.g. 'Europe/Berlin'. Defaults to UTC.
topNoMax results to return (applied after sorting)
extensionNoFilter by extension number on source or destination, e.g. '101'
queueNoFilter by queue number or name, e.g. '802' or 'Support'
scanLimitNoHow many rows to fetch from the server. Increase for busy systems.
Behavior4/5

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

Discloses returns order, record fields, automatic timezone filtering, and required role. No annotations, but missing potential latency or pagination details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and front-loaded with usage examples. Concise but covers key points; could be slightly more terse.

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?

Given 8 parameters and no output schema, the description explains output fields, filters, and requirements fairly completely.

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?

Adds meaningful context beyond schema descriptions, e.g., explaining missedOnly=true usage and timezone-aware filtering.

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 clearly states the tool is for past call history queries with specific examples, distinguishing it from sibling tools like get_active_calls.

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?

Provides explicit use cases and examples, but does not explicitly state when not to use it or mention alternatives like get_active_calls for current calls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SSIG-IT/3cx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server