Skip to main content
Glama

yeastar_catalog

Read-onlyIdempotent

Lists configurable Yeastar PBX resources with their available verbs and supported live operations, including phone reboots, agent pauses, calls, and conferences.

Instructions

Elenco delle risorse configurabili (con i verbi disponibili) e delle operazioni live (riavvio telefoni, pausa agenti, chiamate, conferenze) supportate da questo server.

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": "yeastar_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data and the description correctly does not contradict it. What the description adds is scope: it enumerates the two categories of content the catalog covers (resource verbs and live operations). It does not add anything about freshness, caching, or whether the catalog can vary by account, which limits the credit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, front-loaded with the primary payload (the resource/verb listing) and followed by the secondary payload (live operations). Every phrase carries information; the parenthetical examples clarify scope rather than pad it. A brief opening phrase naming it as the discovery step would have made the structure ideal.

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?

An output schema exists and the tool has no parameters, so return-value details and input semantics are already handled by structured data. The description covers what an agent needs to decide to call it: the catalog spans both configurable resources and live operations. The missing piece is the implied precondition that this is normally the first call in a workflow, which would fully close the loop.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and no risk of ambiguity. The absence of arguments is self-evident from the empty schema, making the description's silence on inputs appropriate rather than a gap.

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 names a concrete deliverable: an inventory of configurable resources with their available verbs, plus live operations (phone reboot, agent pause, calls, conferences). That tells an agent exactly what this tool returns and how it differs from action-oriented siblings like yeastar_apply_change or yeastar_prepare_operation. It stops short of a single crisp verb such as "discover" or "list", leaving the framing mildly implicit.

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 description's content implies this is a discovery entry point that should be consulted before invoking the resource/operation tools, but it never says so explicitly. There is no statement of when not to use it, no prerequisite or ordering guidance, and no pointer to a specific sibling for a follow-up step. Usage must be inferred from the catalog contents.

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