Skip to main content
Glama
WYRE-AI

Cisco Duo MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

duo_list_phones

List phones in your Duo account with optional filters by number or extension to retrieve phone metadata like ID, number, and platform.

Instructions

List phones in the Duo account, optionally filtered by number/extension. Returns phone metadata (phone_id, number, platform/OS, type - PII).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items per page (Duo default/max vary by endpoint).
numberNoFilter by exact phone number.
offsetNoOffset into the result set, for paging past the first page.
extensionNoFilter by extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the response contains phone metadata and flags the data as PII, and 'List' implies a read-only operation. However, it does not mention pagination behavior, rate limits, or permission requirements beyond the PII warning.

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 front-load the action and scope, then the return fields. There is no filler or repetitive content; every sentence adds useful information.

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 low-complexity list tool with fully documented parameters, the description covers purpose, optional filters, and return fields, including a PII flag. It is missing explicit routing to sibling tools and pagination default/max details, but those are minor given the schema coverage and simple operational profile.

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 the schema already documents all four parameters. The description reinforces that number and extension are optional filters but adds no new semantic detail beyond what the schema provides. 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?

The description uses a specific verb, 'List,' with a clear resource: 'phones in the Duo account.' It distinguishes account-level listing from the user-scoped sibling tool by saying 'in the Duo account,' but it does not explicitly name or contrast with duo_list_user_phones or duo_get_phone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool instead of sibling tools such as duo_list_user_phones or duo_get_phone. It states what the tool does but does not provide conditions, exclusions, or alternatives.

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

Deploy Server

Other Tools