Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_list_leads

Read-only

Lists SautiDesk Sales leads the caller may see, newest first, 100 a page (pass next_cursor back as cursor). Filters: view (mine, unassigned, queue, all), status, stage, queue, owner (an id, me or none), tag, source, temperature, next_step (overdue, today, none), contact; sort next_due (default) or newest. Needs SautiDesk Pro and Sales switched on.

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

Input Schema

NameRequiredDescriptionDefault
tagNooptional tag UUID
sortNooptional: next_due (default: overdue first, then next follow-up, then newest) or newest
viewNooptional: mine, unassigned (in a queue, nobody owns it), queue (with queue) or all (default)
limitNooptional page size (max 100)
ownerNooptional owner user UUID, me or none
queueNooptional queue UUID
stageNooptional stage UUID
cursorNonext_cursor from the previous page
sourceNooptional lead source UUID
statusNooptional: open (default), won, lost, closed or all
contactNooptional contact UUID
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.
next_stepNooptional: overdue, today or none (open leads with no open follow-up)
temperatureNooptional: hot, warm or cold

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: page size of 100, cursor-based pagination via next_cursor, default sort semantics (overdue first, then next follow-up, then newest), and the Pro/Sales entitlement requirement.

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 dense sentences, front-loaded with the core action and pagination, then the filter list, then the prerequisite. No filler and nothing buried.

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 14-parameter read tool with no output schema, the description covers pagination, ordering, filtering and entitlement gating well. It does not describe the shape of a returned lead record, which is the main remaining gap given there is no output schema.

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 schema already documents every parameter including enum-like values for view, status, sort and next_step. The description restates the filter vocabulary and the sort default but adds little syntax or format detail the schema lacks, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists SautiDesk Sales leads'), plus scope ('the caller may see') and default ordering ('newest first'). An agent can distinguish it from desk_get_lead (single record) and desk_list_contacts (different resource) without opening the schema.

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

Usage Guidelines4/5

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

Gives clear operating context: the Pro/Sales feature gate, the visibility restriction, and the full filter vocabulary for narrowing results. It stops short of naming alternatives (e.g., desk_get_lead for a single lead, desk_list_contacts for contacts), so there is no explicit when-not guidance.

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