Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_claim_number

Buys a number from the workspace wallet balance (the first month is charged now). Spends money: always confirm the number and price with the user first. Top-ups are not possible through a key.

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": {
      "inventory_id": "<inventory_id>"
    },
    "name": "desk_claim_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
inventory_idYesthe number's inventory_id from desk_search_numbers
idempotency_keyNooptional Idempotency-Key header; a repeat returns the first purchase
expected_monthly_minorNothe monthly price (minor units) the buyer was shown; the claim is refused if it moved

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare openWorldHint and destructiveHint=false, so the description carries the important weight: this spends real money, the first month is charged immediately, and the operation is a commitment the user must approve. That cost-timing and irreversibility context is exactly what annotations do not convey. It stops short of saying whether a purchase can be released or refunded.

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?

Three short sentences, front-loaded with the money-spending fact — the single most important thing an agent must know. Nothing is padded, though the closing top-up sentence is a constraint better placed after the confirmation rule.

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

Completeness3/5

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

Covers the spend, the immediate charge, and the confirm-first rule, which is adequate for a one-required-parameter purchase call with no output schema. It omits preconditions such as sourcing inventory_id via desk_search_numbers and whether a hold must exist first, and does not hint at what a successful claim returns.

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 inventory_id, expected_monthly_minor, and idempotency_key are already fully documented. The description reinforces the price-confirmation workflow that links to expected_monthly_minor but adds no format or syntax detail beyond the schema. 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?

States a specific verb and resource ('Buys a number') plus the funding source ('from the workspace wallet balance'), so the agent knows exactly what the operation is. It does not differentiate from closely named siblings such as claim_number, desk_hold_number, or desk_search_numbers, which matters in a namespace this crowded.

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?

Gives one strong directive — 'always confirm the number and price with the user first' — plus an implied prerequisite that the wallet must already be funded ('Top-ups are not possible through a key'). It offers no routing against alternatives (hold first vs. claim, or how this differs from claim_number), leaving the agent to infer when this is the right tool.

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