Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_create_workspace

Creates another SautiDesk workspace owned by the caller (owner only). It gets its own wallet and its own admin key. Confirm with the user first.

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": {
      "company_name": "<company_name>",
      "country_code": "<country_code>"
    },
    "name": "desk_create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNothe owner's name in the new workspace
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.
company_nameYesthe new workspace's name
country_codeYesISO 3166-1 alpha-2 billing country such as KE; the wallet currency follows from it
idempotency_keyNooptional Idempotency-Key header

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false and openWorldHint=false; the description adds genuinely new behavioral facts, namely that the new workspace 'gets its own wallet and its own admin key' — i.e. it provisions billable, credential-bearing resources. It also discloses the required user-confirmation step. It does not mention whether the new admin key is returned or whether the operation is reversible.

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?

Three short sentences, front-loaded with what is created and the ownership constraint, followed by the side effects and the confirmation requirement. No filler or redundancy.

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?

For a provisioning mutation with no output schema, the description covers the important side effects and the authorization constraint, but leaves unclear what the agent receives back (workspace identifier, admin key, wallet state) and how it differs from the sibling create_workspace. Those gaps matter for a tool that mints credentials and a wallet.

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 is already documented in the schema, including the billing country/currency relationship and the idempotency key. The description adds nothing parameter-specific beyond implying the caller becomes owner. Baseline 3 is appropriate when the schema does the work.

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 ('Creates another SautiDesk workspace') plus the ownership scope ('owned by the caller (owner only)'), which an agent can act on directly. It does not, however, distinguish itself from the sibling 'create_workspace' tool, so the agent cannot tell from the text which creation tool applies in which situation.

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 two concrete usage conditions: the caller must be the owner, and the agent must 'Confirm with the user first' before calling. That is real when-to-use guidance and a prerequisite. It stops short of naming an alternative or saying when this tool should not be used instead of create_workspace.

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