Skip to main content
Glama

yeastar_list

Read-onlyIdempotent

Lists paginated items of a Yeastar PBX resource such as extensions, trunks, queues or CDRs with filtering, sorting and page controls. Use it to browse and find records, then fetch details with yeastar_get.

Instructions

Elenca gli oggetti di una risorsa (paginato). Restituisce i dati base; per il dettaglio usa yeastar_get.

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": {
      "resource": "<resource>"
    },
    "name": "yeastar_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
filtersNoAltri parametri query supportati dall'API
sort_byNoCampo di ordinamento (dipende dalla risorsa)
order_byNo
resourceYesNome risorsa dal catalogo, es. 'extension', 'trunk', 'queue'
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds useful behavior context by saying results are paginated and return base-level data, but it does not add pagination limits, auth requirements, or other operational details beyond the annotations.

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 description is two short sentences and is front-loaded with the core action and scope. Every sentence earns its place: one states the list/pagination behavior, the other routes detail requests to the sibling tool.

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?

An output schema exists and annotations cover safety, so the description need not explain return values or side effects. However, for a six-parameter tool with only 50% schema coverage, it does not provide enough guidance around filters, sorting, or resource catalogs to be fully complete.

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

Parameters2/5

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

Schema description coverage is only 50%, so the description should compensate, but it only mentions pagination generically. It adds no meaning for filters, sort_by, order_by, or resource beyond what the schema already states, and the loosely described page/page_size parameters remain unclarified.

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 states a specific verb and resource: it lists objects of a resource, explicitly notes pagination, and distinguishes the base list from the detailed view handled by yeastar_get. An agent can identify this as the list-versus-get tool without opening the schema.

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?

It explicitly routes detail requests to yeastar_get, giving clear context for when this list tool is appropriate versus that alternative. It does not state exclusions or guidance for choosing between this and other read/search siblings, so it is clear but not fully explicit.

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