Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_get_report

Read-only

Fetches one SautiDesk supervisor report by name (availability, calls, contacts, cost, day, forecast, hourly, league, missed, numbers, occupancy, owed, reasons, recorded, repeat, replies, scorecard, service, spend, staffing, tickets, transfers, webchat, csat (customer satisfaction), week, and the channel reports calls-summary, whatsapp, sms, email). The calls, missed and tickets reports also list their rows, 100 a page in data: pass next_cursor back as cursor (limit and cursor are ignored by the other reports). Needs the Supervisor licence and SautiDesk Pro.

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": {
      "report": "<report>",
      "purpose": "<purpose>"
    },
    "name": "desk_get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNooptional end date/time (YYYY-MM-DD or RFC3339)
tzNooptional IANA timezone, e.g. Africa/Nairobi
fromNooptional start date/time (YYYY-MM-DD or RFC3339)
limitNorows per page for the calls, missed and tickets reports (default and max 100)
cursorNonext_cursor from the previous page of the calls, missed or tickets report
reportYesreport name: availability, calls, contacts, cost, day, forecast, hourly, league, missed, numbers, occupancy, owed, reasons, recorded, repeat, replies, scorecard, service, spend, staffing, tickets, transfers, webchat, csat, week, calls-summary, whatsapp, sms or email
channelNooptional channel filter
purposeYesRequired 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.
agent_idNooptional agent UUID filter (required for AgentScorecard)
queue_idNooptional queue UUID filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / report / description
      Previous value: -"report name: availability, calls, contacts, cost, day, forecast, hourly, league, missed, numbers, occupancy, owed, reasons, recorded, repeat, replies, scorecard, service, spend, staffing, tickets, transfers, webchat, week, calls-summary, whatsapp, sms or email"New value: +"report name: availability, calls, contacts, cost, day, forecast, hourly, league, missed, numbers, occupancy, owed, reasons, recorded, repeat, replies, scorecard, service, spend, staffing, tickets, transfers, webchat, csat, week, calls-summary, whatsapp, sms or email"
  2. 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 (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: the Supervisor licence plus SautiDesk Pro requirement, and the fact that only calls/missed/tickets paginate while limit and cursor are silently ignored elsewhere. It stops short of describing the shape of non-paginated report responses.

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?

One dense but front-loaded paragraph that leads with the verb and resource; no filler sentences. The 29-name parenthetical is largely duplicated by the schema's report description, which is the main wasted space.

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 10-parameter, no-output-schema tool, the definition covers valid report names, pagination semantics and licence prerequisites, which is most of what an agent needs. Minor gaps: it doesn't say what non-paginated reports return or that agent_id is mandatory for the scorecard report.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: pagination applies only to three reports, limit/cursor are ignored by the rest, and rows come back under `data` with a `next_cursor` to feed back as `cursor`. It still restates the report-name list that the schema already documents.

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?

Names a specific verb and resource ('Fetches one SautiDesk supervisor report by name') and enumerates the exact set of valid report names, so an agent knows precisely what it retrieves. It does not differentiate from adjacent siblings such as get_call_stats, get_broadcast_report, get_dialer_report or desk_get_admin_dashboard, which also return metrics.

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: the report-name list lets an agent infer which report answers which question, and the 'Supervisor licence and SautiDesk Pro' line sets a prerequisite. There is no explicit when-to-use versus the other reporting siblings, and no statement of when a plain list/get tool would be preferable.

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