Sautikit

create_workspace

Creates a new workspace/tenant you own. Confirm with the user. Spends nothing, but establishes a new billing tenant. Requires the account.manage permission granted at connect time.

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": {
      "name": "<name>",
      "country": "<country>",
      "currency": "<currency>"
    },
    "name": "create_workspace"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	the workspace/organization name
`country`	Yes	ISO-3166-1 alpha-2 country code, e.g. KE, UG, TZ
`purpose`	No	Required 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.
`currency`	Yes	ISO-4217 currency code, e.g. KES, UGX, TZS

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description adds genuinely new context about cost ("Spends nothing"), a side effect ("establishes a new billing tenant"), and an auth requirement. That is substantial disclosure beyond structured fields, though it says nothing about failure modes or name uniqueness.

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?

Four short sentences, each carrying distinct information (effect, confirmation, cost/billing, permission), with the core action front-loaded. Slightly fragmented in rhythm but no wasted wording.

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 mutation tool with no output schema, the definition covers the important agent-facing risks: cost, billing-tenancy side effect, required permission, and the need to confirm. The main gap is the absence of any routing hint relative to the sibling workspace-creation tool.

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%, with name, country, currency, and purpose all documented in the schema itself, so the baseline is 3. The description adds no format or constraint detail beyond the schema, so it neither compensates nor detracts.

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 a new workspace/tenant you own") so an agent immediately knows the effect. It does not, however, distinguish this from the sibling desk_create_workspace, leaving ambiguity about which creation tool applies in a desk context.

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 a clear operational prerequisite ("Requires the account.manage permission granted at connect time") and a caution ("Confirm with the user"). It stops short of saying when to prefer this over a sibling such as desk_create_workspace, so routing between the two remains implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sautikit tools Inspect

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

Need Help?