Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_list_api_key_people

Read-only

The people the caller may issue an API key for (a key acts as one person), in data; you is who the caller acts as. Pages 100 at a time: 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_list_api_key_people"
  }
}

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 establish this as a safe, non-destructive, closed read. The description adds value beyond them by disclosing the page size (100), the cursor round-trip, and the response shape (`data` for people, `you` for the caller's identity). It does not mention permissions or ordering, but the core behavior is clear.

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 compact sentences, with the resource definition front-loaded ahead of pagination mechanics; no filler. The semicolon-joined return-shape clause is slightly dense but still earns its place.

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 simple, read-only, three-parameter list tool with full schema coverage and no output schema, the description covers scope, pagination, and the top-level response keys. Only minor gaps remain, such as what fields each person carries, which an agent can discover from the response.

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 already documented in the schema, and the description merely restates the cursor round-trip ('pass next_cursor back as cursor'). It adds no meaning about page-size limits or the `purpose` field beyond what the schema provides, so the baseline 3 applies.

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 the resource precisely ('the people the caller may issue an API key for') and clarifies the domain concept that a key acts as one person. It implicitly lists them into `data`, though it never uses an explicit verb like 'list', and it does not name the sibling it differs from (e.g. desk_list_keys_issued_by or desk_list_api_keys).

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?

The framing ('may issue an API key for') implies the use case of finding a person to pass to desk_create_api_key, and the pagination sentence gives operational guidance. However, there is no explicit when-to-use/when-not statement and no routing against the closely related key-listing siblings.

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