Dialpad MCP server

dialpad_get_callcenter

Read-onlyIdempotent

Retrieve a call center by ID to review its routing, operating hours, and alert settings.

Instructions

Get one call center by ID, including its routing, hours and alert settings.

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": {
      "id": "<id>"
    },
    "name": "dialpad_get_callcenter"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Call center ID (numeric).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by naming the categories of data returned (routing, hours, alert settings), but says nothing about error behavior for invalid IDs or whether missing fields can occur.

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?

A single front-loaded sentence with the action, the key, and the payload all stated up front. No filler or redundant restatement of the tool name.

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 one-parameter read tool with full annotation coverage and no output schema, the description supplies enough to call it correctly and to know roughly what comes back. Only minor gaps remain around failure modes and the exact shape of the returned settings.

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?

Schema coverage is 100% with a single required parameter already documented as "Call center ID (numeric)". The description only repeats "by ID" without adding format, sourcing, or lookup guidance, so the baseline of 3 applies when the schema carries the burden.

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 verb and resource ("Get one call center") plus the retrieval key ("by ID") and enumerates the data returned (routing, hours, alert settings). This clearly separates it from dialpad_list_callcenters and dialpad_get_callcenter_status, though no sibling is named explicitly.

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?

The phrase "one call center by ID" implies single-record lookup rather than listing, but there is no explicit when-to-use guidance, no mention of when to prefer dialpad_get_callcenter_status, and no stated prerequisites such as needing a known ID first.

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