Skip to main content
Glama

yeastar_get

Read-onlyIdempotent

Retrieve full configuration of a Yeastar PBX resource or global setting by name and optional ID to inspect extensions, trunks, routes, IVRs, queues, and feature codes before editing.

Instructions

Configurazione completa di un oggetto (o di un'impostazione globale).

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoID univoco (non il numero interno). Omesso per le impostazioni globali.
resourceYesNome risorsa, es. 'extension' o un'impostazione globale come 'feature_codes'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive operation, and the description does not conflict with them. Beyond those fields, "complete configuration" adds useful result-scope context, but there is no information about missing resources, invalid IDs, or other runtime behavior.

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?

The single short phrase is economical, front-loads the full-configuration scope, and contains no filler. Its noun-phrase form sacrifices some immediacy; an explicit retrieval verb would improve clarity without meaningfully increasing its length.

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?

For a simple two-parameter read with fully described inputs, safety annotations, and an output schema, the definition is minimally sufficient for invocation. It remains weak for tool selection because it does not distinguish this full-configuration getter from other read-oriented siblings or describe relevant failure behavior.

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 description coverage is 100%, including resource examples and the rule that `id` is a unique ID omitted for global settings. The description's object/global-setting wording adds little parameter meaning beyond that documentation, so the baseline score applies.

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

Purpose3/5

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

The Italian text means "complete configuration of an object (or a global setting)," identifying the resource and full-configuration scope. However, it supplies no retrieval verb or sibling differentiation, so the read action must be inferred from the name `yeastar_get` and the annotations.

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 wording implies use when an object's complete configuration or a global setting is needed. It does not explain when this tool is preferable to other read-oriented operations, nor provide prerequisites, exclusions, or alternative-tool routing.

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