Skip to main content
Glama
Sign In
Wagner-Emden-IT-Services

placetel-web-api-mcp-server

by Wagner-Emden-IT-Services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Fetch all call center queues

placetel_list_call_center_queues
Read-onlyIdempotent

Fetch all Placetel call center queues to inspect routing groups, with pagination and markdown or JSON output. Read-only.

Instructions

Fetch all call center queues. (GET /call_center_queues) Read-only.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
per_pageNoItems per page (max 100). Not honored by every endpoint.
response_formatNoOutput format: 'markdown' (human-readable, default) or 'json' (machine-readable).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

The description reiterates that the operation is 'Read-only' and provides the HTTP endpoint. Since annotations already provide comprehensive safety context (readOnlyHint, destructiveHint), the description adds minimal new behavioral information beyond redundancy.

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?

The definition is highly concise, front-loading the core purpose while providing essential context (the GET endpoint) in a single, effective statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It is minimally complete. Given the presence of pagination parameters, the description could benefit from noting that these parameters control the volume of the returned list.

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?

Since the schema coverage is 100%, the schema already defines all parameters (`page`, `per_page`, `response_format`) adequately. The description provides no value that isn't present in the structured data, meeting the minimum viability score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the function (Fetch) and the resource (call center queues). This is unambiguous and distinguishes it from creation or detail retrieval tools.

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

Usage Guidelines4/5

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

While it doesn't explicitly mention how to handle filtering or errors, the name 'list' implies the intended use case. It is clear that this tool is used to retrieve the catalog of existing queues.

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