Skip to main content
Glama

yeastar_pending_changes

Read-onlyIdempotent

List prepared PBX configuration changes awaiting confirmation before they expire. Review staged changes to confirm or discard them within the change TTL window.

Instructions

Elenca le modifiche preparate in attesa di conferma (scadono dopo CHANGE_TTL_SECONDS).

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

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
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description doesn't need to restate safety. It does add a genuinely new behavioral fact beyond the annotations — that entries expire after CHANGE_TTL_SECONDS — which tells the agent the list is time-limited, although the constant itself is left unexplained.

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?

One compact parenthetical-bearing sentence with no filler, and the core purpose is front-loaded ahead of the expiry caveat.

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?

With an output schema present, the description needn't explain return shape, and annotations cover the safety profile. For a no-parameter read tool this is close to sufficient, with only the unelaborated TTL constant as a loose end; the Italian-only wording is a minor friction for English-oriented agents.

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 there is no parameter semantics to document; baseline is 4. The schema is an empty object and the description correctly spends no words on arguments.

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: 'Elenca le modifiche preparate in attesa di conferma' describes listing queued-but-unconfirmed changes. That distinguishes it reasonably well from the mutate-side siblings, though it never names apply_change or cancel_change as the tools that act on the listed items.

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?

Usage is only implied: an agent can infer it should call this before applying or cancelling pending changes, but the description never says when to call it, nor that the returned changes must be applied before expiry. No explicit alternative or exclusion is given.

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