Skip to main content
Glama

yeastar_query

Read-onlyIdempotent

Retrieve details for multiple PBX objects of a specified resource type in one request using up to 100 IDs, avoiding repeated single-item queries.

Instructions

Configurazione completa di più oggetti in una sola chiamata.

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>",
      "ids": "<ids>"
    },
    "name": "yeastar_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesLista di ID univoci
resourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description's only added value is that multiple objects are fetched in one call. It omits what happens when an ID is unknown or not permitted, whether the response is partial or an error, and how the 100-ID cap behaves. The word "configurazione" also leans toward write semantics and creates avoidable ambiguity against the read-only annotation, though it does not clearly contradict it.

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

Conciseness3/5

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

One short sentence with no padding, so nothing is wasteful, but it is under-specified rather than concise. There is no structure beyond a single clause, and it is written in Italian while the rest of the tool surface is English, which is a small consistency cost.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but that is the only thing covered. For a two-required-parameter batch lookup whose 'resource' parameter has neither description nor enum, the definition leaves the single most important input unspecified and gives no routing against the many sibling lookup tools.

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?

The description says nothing about either parameter. Schema coverage is only 50%: 'ids' is documented as "Lista di ID univoci" but 'resource' has no description and no enum, so the agent is left guessing which resource type strings are valid. The description had a clear opportunity to enumerate allowed resource values and did not take it.

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

Purpose2/5

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

"Configurazione completa di più oggetti in una sola chiamata" contains no operative verb — 'configuration' is a noun and it never says whether the tool reads, returns, or applies settings for the listed objects. The name (yeastar_query) and the readOnly annotation point to a batch read, but the description itself does not state that, and nothing distinguishes it from yeastar_get, yeastar_read, yeastar_list, or yeastar_search.

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?

There is no when-to-use guidance, no exclusion, and no mention of any alternative despite a large sibling set of lookups (yeastar_get, yeastar_read, yeastar_list, yeastar_search). At most the phrase "in una sola chiamata" hints at batch usage, which is the only usage signal present.

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