Skip to main content
Glama

yeastar_overview

Read-onlyIdempotent

Retrieve PBX model, firmware version, extension and concurrent-call capacity, plus MCP server status to confirm connectivity and start Yeastar P-Series administration.

Instructions

Informazioni generali sul centralino: modello, versione firmware, capacità (interni, chiamate contemporanee) e stato del server MCP. Usalo come primo controllo della connessione.

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

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.9/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, so the safety profile is fully covered by structured data. The description adds that the call reports MCP server status as a connection diagnostic, which is useful behavioral context, but says nothing about failure modes or what an unconnected state looks like.

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 short sentences with no waste: the returned data is front-loaded and the usage cue follows. Every clause earns its place.

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?

For a no-parameter read tool with full annotation coverage and an output schema, the description supplies the essential information: what is returned and when to call it. It leaves only minor gaps, such as whether the call fails when the PBX is unreachable.

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 the baseline is 4 and there is no parameter meaning the description could or should add. Nothing is obscured.

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 the concrete resource (il centralino / PBX) and enumerates exactly what the tool returns: model, firmware version, capacity (extensions, concurrent calls) and MCP server status. That is far more specific than a restatement of the name, though it does not explicitly contrast itself with siblings like yeastar_get or yeastar_list.

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?

"Usalo come primo controllo della connessione" gives a clear conditional use case — call this first to verify connectivity before other operations. It gives context but no explicit when-not-to-use or named alternative, so it falls short of a 5.

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