Dialpad MCP server

dialpad_get_call

Read-onlyIdempotent

Retrieve detailed information for a single Dialpad call, including timings, routing, recording details, CSAT score, and AI transcription text when available.

Instructions

Get one call in detail: timings, routing, recording details, CSAT score and AI transcription text if any. Dialpad allows 10 of these per minute. Contains personal information - admin-gated.

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

Input Schema

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

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 establish read-only, idempotent, non-destructive, open-world behavior, so the description adds real value beyond them: a concrete rate limit (10/minute), an authorization constraint (admin-gated), and a data-sensitivity warning (contains personal information). What it lacks is any note on error behavior for invalid or deleted IDs, which matters for a lookup tool.

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?

Three compact clauses: what is returned, the rate constraint, the access and privacy constraint. The valuable content is front-loaded and no sentence is filler.

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-parameter read tool with strong annotations and a fully documented schema, the description covers purpose, limits, and access gating. It stops short of describing the response shape or behavior on missing/inaccessible calls, which is the only meaningful remaining gap.

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% and the sole parameter is documented there as 'Call ID (numeric).' The description adds nothing about the ID beyond the implicit 'one call,' so the schema is doing all the parameter work — baseline 3 is appropriate.

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?

Names a specific verb and resource ('Get one call in detail') and enumerates the returned facets: timings, routing, recording details, CSAT, AI transcription. That distinguishes it from list-type siblings, but it does not address overlap with the very similar dialpad_get_call_transcript, which an agent could reasonably confuse it with.

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 singular 'one call' plus the required ID implies a by-identifier fetch rather than a search or listing, and the stated 10-per-minute cap implicitly discourages bulk looping. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to dialpad_get_call_transcript for the transcription-only case.

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