Skip to main content
Glama

yeastar_search

Read-onlyIdempotent

Search Yeastar PBX objects by number or name and retrieve the IDs needed for get, update, or delete operations on extensions, trunks, routes, and other resources.

Instructions

Cerca oggetti per numero o nome. Serve anche a trovare l'id da usare in get/update/delete.

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>",
      "search_value": "<search_value>"
    },
    "name": "yeastar_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
filtersNo
resourceYesNome risorsa, es. 'extension'
page_sizeNo
search_valueYesTesto da cercare (numero, nome, ...)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds the useful framing of this as an id-lookup step in a workflow, but says nothing about match semantics (exact vs substring), empty-result behavior, or pagination despite page/page_size existing.

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 tight sentences, front-loaded with the core action and followed by the practical purpose; nothing is redundant.

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 and annotations are present, so return values and safety are covered. However, for a 5-parameter tool with three undocumented parameters, the description should at least mention paging and how filters narrow results; that gap keeps it at minimum viable.

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 coverage is only 40%: resource and search_value are documented, while page, page_size and filters carry no description and the description does not compensate for them. It does clarify that search_value accepts a number or a name, but leaves filters and paging semantics entirely to inference.

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 ('Cerca oggetti per numero o nome') and adds a concrete secondary purpose: recovering the id needed by get/update/delete. It does not differentiate this from siblings like yeastar_list, yeastar_query or yeastar_read, so an agent still has to guess the boundary.

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?

Gives one clear when-to-use case (resolving an id before get/update/delete) and the searchable keys (number, name), but never says when to prefer this over list/query/read, nor what happens when the id is already known.

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