Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_get_phone_menu

Read-only

The workspace's one phone menu: its settings in menu (null when there is none) and its keys, by digit, as the paged data. Pages: pass next_cursor back as cursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNopage size (default and max 100)
cursorNonext_cursor from the previous page
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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds value on top: it discloses the null-when-absent edge case for `menu` and explains that the paged payload is the digit keyed entries, which prevents an agent from mishandling a workspace with no menu configured. Rate/permission behavior is not covered, keeping it below a 5.

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?

Two short sentences with the resource identity and the return shape front-loaded, followed by the paging rule. Slightly odd phrasing ('by digit, as the paged data') costs a little clarity but no sentence is 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?

There is no output schema, so the description must carry the return shape and it does: a `menu` settings object or null, plus paged key entries. For a zero-required-parameter read tool, that plus full schema coverage is close to sufficient; only the `purpose` parameter's expectation is left unaddressed.

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 `limit`, `cursor`, and `purpose` are fully documented in the schema and the baseline of 3 applies. The description restates the cursor round-trip ('pass next_cursor back as cursor') and clarifies that pagination applies to the keys rather than the settings object, which is a small but real addition; nothing is said about `limit` or `purpose`.

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 resource and scope: 'The workspace's one phone menu', a singleton, and describes what is returned (settings in `menu`, keys by digit). An agent can tell this reads menu/IVR configuration rather than contacts or numbers. It does not name a sibling alternative the way a top-tier definition would, but no sibling in the list covers phone menus, so ambiguity is low.

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?

Pagination usage is spelled out ('pass next_cursor back as cursor'), which is genuine operational guidance. There is no when-to-use framing, no note that this is the only way to read menu configuration, and no mention of the `purpose` parameter's requirement despite it being documented as required for read tools in the schema.

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