Dialpad MCP server

dialpad_list_numbers

Read-onlyIdempotent

Lists company phone numbers with type, status, and assignment details for users, offices, departments, or call centers; requires an admin API key.

Instructions

List phone numbers in the company with type, status, and what each is assigned to (user, office, department, call center). Needs a company admin API key.

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

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.
`status`	No	Number status filter, e.g. available or assigned.
`area_code`	No	Area code, digits only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, and the description adds genuinely useful context not in annotations: the required company-admin credential and the shape of the returned assignment data. It omits pagination behavior, which the cursor parameter implies but the text never explains.

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 short sentences with zero waste: the resource and returned fields come first, and the credential requirement follows. Nothing is redundant or buried.

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 read-only list tool with four optional parameters and no output schema, the description covers what the tool returns and what access it needs. Only pagination behavior is left implicit, which the schema's cursor description partially handles.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description adds no parameter-level detail (e.g., how status or area_code interact with results), so baseline 3 applies.

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 uses a specific verb (List) and resource (phone numbers in the company) and enumerates the fields returned plus the assignment targets (user, office, department, call center). It is clear without opening the schema, though it does not explicitly differentiate itself from siblings like dialpad_get_number or dialpad_list_users.

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 implied by 'List phone numbers in the company' and a prerequisite is stated ('Needs a company admin API key'), which helps an agent decide the call will succeed. However, there is no explicit when-to-use vs. dialpad_get_number guidance or any statement of when not to call it.

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