Skip to main content
Glama

yeastar_prepare_raw

Read-only

Prepares a direct call to a PBX API endpoint not covered by the catalog, acting as a fallback escape hatch. Returns a preview that must be confirmed before applying.

Instructions

PREPARA una chiamata diretta a un endpoint non coperto dal catalogo (escape hatch). Nessun diff automatico: usa solo se le altre funzioni non bastano. Va confermata con yeastar_apply_change.

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": {
      "method": "<method>",
      "endpoint": "<endpoint>"
    },
    "name": "yeastar_prepare_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoBody JSON per le POST
methodYes
paramsNo
endpointYesEndpoint API, es. 'holidays/import' o 'backup/delete'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: there is no automatic diff and the prepared call is inert until confirmed via yeastar_apply_change, which is exactly the trait an agent needs for a raw POST escape hatch. Auth requirements and error behavior for invalid endpoints remain unstated.

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?

Three short sentences, front-loaded with the escape-hatch caveat, the 'no automatic diff' warning, and the required confirmation. Every sentence carries decision-relevant information with no filler.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, restriction, and the confirmation workflow. For a 4-parameter raw-endpoint tool the remaining gap is parameter-level guidance, particularly the undocumented 'params' field and method/body interaction.

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?

Schema description coverage is only 50%: 'endpoint' and 'body' are documented in the schema, but 'params' has no description anywhere and 'method' is only an enum. The description mentions no parameters at all, so it fails to compensate for the gap (e.g. when GET vs POST applies, or whether body is ignored on GET).

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 a specific verb and resource ('PREPARA una chiamata diretta a un endpoint') and frames it as an escape hatch for endpoints outside the catalog, which distinguishes it from the catalog-driven prepare siblings. It stops short of naming which sibling is the default path, leaving that inference to the reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not rule ('usa solo se le altre funzioni non bastano') and a mandatory follow-up ('Va confermata con yeastar_apply_change'), naming the sibling that completes the flow. An agent knows both the entry condition and the exit path without further inference.

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