Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_list_contacts

Read-only

Lists or searches SautiDesk contacts.

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

Input Schema

NameRequiredDescriptionDefault
qNosearch query (name, phone, email, organization)
limitNooptional page size (default and max 100)
cursorNonext_cursor from the previous page
offsetNolegacy pagination offset; prefer cursor
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of pagination behavior, whether an empty query returns everything, or result limits at the 100-record cap implied by the schema.

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 under-specification rather than disciplined conciseness, which is penalized in the completeness dimension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter search/list tool with two competing pagination modes (cursor and legacy offset) and no output schema, the description should explain result shape and paging expectations. It leaves the agent to reconstruct all of that from the schema alone.

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 every parameter including the q, limit, cursor, offset, and purpose fields is already documented in the schema with examples. The description adds no meaning beyond that, which is the expected baseline for a fully documented schema.

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?

The description names a specific verb pair (lists or searches) and a specific resource (SautiDesk contacts), so an agent knows what the tool returns. It does not, however, distinguish this from sibling desk_lookup_contact, which is the closest available alternative for retrieving a contact.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of desk_lookup_contact, desk_list_tickets, or the other list tools. The reader must infer from the name alone that this is the bulk-enumeration entry point while desk_lookup_contact is the single-record one.

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