Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_place_call

Places an outbound call as the acting person: rings their device first, then the number. The call is billed to the workspace wallet: confirm with the user first.

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": {
      "to": "<to>"
    },
    "name": "desk_place_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesnumber to call (E.164, or as written locally)
fromNooptional workspace number to call from (caller ID)
deviceNooptional device to ring first
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still adds real behavioral context: the device rings first, then the destination, and the call is billed to the workspace wallet. That cost/auth-to-wallet detail and the two-stage ringing sequence are exactly the kind of trait annotations cannot express.

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, zero filler, and the core action is front-loaded ahead of the cost warning and confirmation instruction. Nothing could be removed without losing information.

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 call-placing action with no output schema, the description covers the mechanics, the billing consequence, and the required user confirmation, which is enough to call it responsibly. It stops short of saying what comes back (e.g., a call ID usable with `get_call` or `hangup_call`), a minor remaining gap.

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 coverage is 100%, so the schema already documents `to`, `from`, `device`, and `purpose` with formats. The description adds only implicit meaning for `device` via "rings their device first" and nothing about `from` as caller ID, so the 100%-coverage baseline of 3 is correct.

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 ("Places an outbound call") plus the acting-person scope, which is concrete and unambiguous. It does not differentiate from the sibling `place_call` or `send_agent_call`, both of which plausibly place calls, so the agent cannot tell which of these to pick from the description alone.

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?

Gives one genuine precondition — "confirm with the user first" — which is actionable when-to guidance before dialing. However, it offers no routing guidance against `place_call`, `send_agent_call`, or `desk_transfer_call`, and no statement of when not to use it, so the usage guidance is only partly implied.

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