Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

claim_number

SPENDS MONEY: claim an available number for this workspace; charges a prorated amount now (the first_charge_total_minor from search_available_numbers, VAT included only while VAT is in force) and a monthly rental thereafter. Always confirm with the user first. Pass idempotency_key to make retries safe, and expected_monthly_minor (the monthly_price_minor from search_available_numbers) so a price that moved is refused with numbers.price_changed instead of charged.

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": "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_idYesinventory_id of an available number (from search_available_numbers)
idempotency_keyNoclient-chosen key so a retried claim does not double-charge
expected_monthly_minorNothe monthly_price_minor search_available_numbers showed for this number; if the price moved the claim is refused with numbers.price_changed and nothing is charged

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say openWorldHint=false and destructiveHint=false; the description supplies the real behavioral picture — a prorated charge at claim time, an ongoing monthly rental, VAT treatment, and the exact refusal path (numbers.price_changed) with no charge. That is exactly the money-and-side-effect context the annotations cannot convey.

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?

Front-loaded warning, then mechanics, then the two safety parameters — every clause carries information and nothing is repeated across sentences despite the density.

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 money-spending mutation with no output schema, it covers cost, timing, confirmation, idempotency, and the failure mode well; it stops short of saying what a successful claim returns (e.g. the provisioned number record), which is the one remaining gap.

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 already 100%, so baseline is 3; the description still adds value beyond the schema by explaining why idempotency_key matters (retry safety) and by tying expected_monthly_minor to the specific price-change refusal outcome and the sourcing of first_charge_total_minor from search_available_numbers.

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 ('claim an available number for this workspace') and front-loads the consequence ('SPENDS MONEY'), which cleanly separates it from search_available_numbers (the read side) and from non-spending siblings like list_numbers.

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 explicit operating guidance: confirm with the user first, pass idempotency_key for safe retries, pass expected_monthly_minor to refuse a moved price. It does not name competing siblings such as desk_claim_number or desk_hold_number, so the when-not/alternative routing is left implicit.

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