Skip to main content
Glama

Get call center status

get_call_center_status
Read-onlyIdempotent

Whether the call centre is connected for this account, whether agents can place calls from the dashboard, and when its contacts were last synced. active is false when it is not set up, which is why such an account has no call data.

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_call_center_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds genuine semantic context beyond that: it explains that active=false means the account is not configured, and that this explains the absence of call data — a diagnostic interpretation an agent could not derive from annotations alone.

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?

Two compact sentences with no filler: the first front-loads the returned state, the second explains the failure mode. Nothing is repeated and nothing could be removed without losing meaning.

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 single-optional-parameter, read-only status tool with no output schema, the description covers what is returned and how to interpret the key boolean. It stops short of describing filtering behavior of the fields parameter or any error/permission conditions, but nothing essential for correct invocation 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 one optional parameter at 100% schema coverage, the baseline is 3; the description earns the extra point by defining the meaning of each selectable field value (active, can_originate, contacts_synced_at) in plain language, which is exactly what the fields parameter filters on.

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 names a specific resource (call centre status for this account) and enumerates exactly what is returned: connection state, whether agents can originate calls, and the contact sync timestamp. It doesn't explicitly contrast itself with siblings like get_contact_center_live_overview, but the 'status/configuration' framing is distinct enough to identify the tool's job.

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 is only implied: an agent can infer this is the pre-check to run before trusting call data, especially from the closing note that an unset-up account has no call data. There is no explicit statement of when to call it versus alternatives, and no prerequisites or sequencing guidance.

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