Dialpad MCP server

dialpad_get_contact

Read-onlyIdempotent

Retrieves a single shared or local contact by ID, including admin-gated personal details, so you can look up contact information in Dialpad.

Instructions

Get one shared or local contact by ID. 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_contact"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Contact ID.

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 declare readOnly, idempotent, non-destructive behavior, so the description is not needed for the safety profile. It still adds genuinely non-obvious context: the record contains personal information and access is admin-gated, which tells the agent to expect an authorization failure for non-admin callers. It does not describe not-found behavior or return shape, but the key access constraint is disclosed.

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 the core operation front-loaded and the access caveat second. No filler, no restatement of the title, and every clause carries information an agent can act on.

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 single-record read with full schema coverage, rich annotations, and no output schema, the description covers purpose, scope, and the admin-gating constraint. The only notable omission is failure behavior when the ID does not exist, which is minor at this complexity.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the contact ID fully. The description's "by ID" restates rather than extends that meaning, adding no format, source, or constraint details. This is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("Get one ... contact") plus the scope (single record, by ID, shared or local). An agent can distinguish this from dialpad_list_contacts because the description specifies one record retrieved by ID. It stops short of naming the list sibling as the discovery path, but the operation itself is unambiguous.

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: call this when you already have a contact ID. The description does not say how to obtain an ID (e.g., via a list/search tool) or what to do if the ID is unknown, so the when-to-use guidance is only partially covered. No explicit exclusions are given.

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