Skip to main content
Glama
Dialpad MCP server

Dialpad MCP server

dialpad_list_departments

Read-onlyIdempotent

Lists company departments (ring groups), optionally filtered by office or name, to help you locate the right group before managing or routing calls.

Instructions

List departments (ring groups) 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_departments"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn every field of each item instead of the main fields only. Larger output; use only when needed.
cursorNoCursor from next_cursor of the previous page, to get the next page.
office_idNoOnly departments in this office.
name_searchNoText to match in the department name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 fully covered without the description. The description adds only the scope detail that the default is company-wide rather than office-limited; it says nothing about pagination limits, result ordering, or auth/permission requirements, so it contributes modestly beyond the structured data.

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 short sentence with the resource and its scope front-loaded and no filler. Every clause carries information: the resource, its domain synonym, and the default scope.

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 complete schema documentation and full annotation coverage, the definition covers the essentials. The only shortfall is that pagination behavior and what a returned department record contains are left entirely to the schema's cursor and full parameter descriptions.

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%, and each parameter (full, cursor, office_id, name_search) is documented in the schema itself, so the baseline is 3. The description's "optionally for one office" merely restates the office_id parameter and adds no syntax, format, or matching-behavior detail beyond what the schema provides.

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 ("List departments") and disambiguates the domain term by glossing it as "(ring groups)", which an agent could not infer from the name alone. It is clearly distinguishable from the singular dialpad_get_department sibling by the list semantics, though it never names that sibling 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 office-scoped variant of the call, which is useful, but there is no explicit statement of when to prefer this over dialpad_get_department or how to page through results. Usage is implied rather than prescribed.

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