Skip to main content
Glama

Get contact center live overview

get_contact_center_live_overview
Read-onlyIdempotent

What is happening right now across the account: campaigns running or paused with their agents per state (ready, ringing, in_call, wrap_up, paused, offline) and active calls, a summary, and supervisor alerts (a break over its limit, a running campaign with contacts pending and nobody to take them).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_contact_center_live_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds useful content-level context about what is returned and what triggers supervisor alerts, but does not mention freshness/latency, result size, or any operational behavior beyond the annotations.

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?

A single front-loaded sentence opens with 'What is happening right now' and then lists the returned sections. It is dense but every clause carries content; no filler or repetition.

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 simple read-only overview tool with no output schema and one optional filter, the description covers the returned sections and alert meanings adequately. Minor gaps around freshness and response shape are acceptable given the annotations and simple schema.

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?

The single optional 'fields' parameter has 100% schema coverage, establishing a baseline of 3. The description's enumeration of summary, campaigns, and alerts loosely mirrors the enum values, but it adds no filtering syntax or behavior beyond what the schema already documents.

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?

The description states a concrete resource and scope: live account-wide contact-center state, including campaign/agent states, active calls, summary, and supervisor alerts. It is distinguishable from narrower siblings like get_agent_report or get_live_conversation_metrics because of the account-wide, multi-section snapshot framing, though it never explicitly contrasts them.

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

Usage Guidelines2/5

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

The phrase 'right now' implies a real-time snapshot, but there is no explicit when-to-use guidance and no named alternative such as get_agent_report, get_account_summary, or get_live_conversation_metrics. An agent has to infer the routing decision from the content list alone.

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