Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_transfer_call

Initiates a blind or attended transfer for an active SautiDesk call.

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": "desk_transfer_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
ticket_idNooptional: the ticket the call is shown on, to help find the call
target_agent_idNoteammate (user UUID) to put the caller through to
target_queue_idNoqueue UUID to put the caller into (give this or target_agent_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, lowering the bar. The description adds the important 'active call' precondition and the blind/attended distinction, but never explains how that choice is expressed (it appears to be implicit in supplying target_agent_id vs target_queue_id) or what happens to the transferring agent.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity is part of why behavioral detail is thin rather than a model of tight structure.

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 mutation on a live call with no output schema, the definition covers the minimum: target options are documented fully in the schema and safety flags exist in annotations. What is missing is what an agent most needs at call time — how to choose blind vs attended, and what confirms success or failure.

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%, so the baseline is 3. The mention of 'blind or attended' hints that the two target parameters correspond to different transfer modes, but the mapping is left implicit and the description adds nothing about the ticket_id or purpose parameters.

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 ('Initiates') plus resource ('transfer for an active SautiDesk call') and even names the two modes (blind vs attended). It is clearly distinguishable from siblings like desk_wrap_call or handoff_dialer_call, though it never explicitly contrasts itself with them.

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 phrase 'active SautiDesk call' implies the precondition that a call must be in progress, but there is no explicit when-to-use guidance, no when-not, and no mention of the closest alternative, handoff_dialer_call, which also moves a caller elsewhere.

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

All Sautikit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources