Dialpad MCP server

dialpad_list_callcenters

Read-onlyIdempotent

List call centers (queues) across a company or filter by office/name, with pagination and optional full details.

Instructions

List call centers (queues) across the company, optionally for one office.

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": "dialpad_list_callcenters"
  }
}

Input Schema

Name	Required	Description
`full`	No	Return every field of each item instead of the main fields only. Larger output; use only when needed.
`cursor`	No	Cursor from next_cursor of the previous page, to get the next page.
`office_id`	No	Only call centers in this office.
`name_search`	No	Text to match in the call center name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.7/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 fully covered by structured data. The description adds nothing beyond that — it does not mention pagination behavior or result ordering, and the cursor paging is only discoverable from the schema. Adequate but minimal given the low bar set by annotations.

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 sentence with zero filler, front-loading the resource and stating the key optional scoping in one clause. Nothing is restated redundantly from the schema or annotations.

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 list tool with full schema description coverage, complete annotation coverage, and no output schema, this is close to sufficient. The only real gap is a brief note on paging (cursor/next_cursor) and whether results are company-wide by default, which would remove the last bit of inference.

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?

Schema coverage is 100%, so baseline is 3, and the description adds a small amount by framing office_id as optional office-level scoping in plain language. It does not explain the paging cursor or the 'full' field-expansion tradeoff, but those are already well documented in the schema descriptions.

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?

Description pairs a specific verb ("List") with a specific resource ("call centers (queues)") and states scope ("across the company"). The "(queues)" gloss disambiguates terminology, and the singular-get sibling dialpad_get_callcenter is implicitly distinguishable by the list framing, 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?

"Optionally for one office" implies the filtering use case, and the name_search/full params suggest narrowing behavior. However, there is no explicit statement of when to use this versus dialpad_get_callcenter or dialpad_get_callcenter_status, and no stated exclusions or prerequisites.

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