Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

get_wallet_balance

Read-only

Current wallet balance (minor units), currency, low-balance threshold, and status.

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": "get_wallet_balance"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavioral detail: amounts are returned in minor units, and the payload also carries a low-balance threshold and a status field, which an agent could not otherwise predict since there is no output schema. Scope (account-wide vs per-workspace) and data freshness are still unstated.

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?

One short sentence with zero filler, and the most important content (balance in minor units) leads. It reads as a field list rather than a complete sentence, which slightly weakens the framing but costs no space.

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 zero-required-parameter read tool with no output schema, listing the returned fields is the right instinct and covers the return shape. However, it leaves out the wallet's scope and any pointer to the statement or spend siblings, which is the main thing an agent still needs to know before calling it.

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?

The single parameter is the generic 'purpose' field and its schema description is fully documented, so the schema carries the whole burden. The description adds nothing about it, but at 100% schema coverage the baseline of 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 a specific resource and what is retrieved from it: the current wallet balance, plus currency, low-balance threshold, and status. The purpose is unambiguous, but it does not distinguish this from near siblings such as list_wallet_statements or get_ai_spend, and it is phrased as a noun fragment rather than an action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the alternatives an agent could reach for instead (list_wallet_statements for history, get_ai_spend for spend detail). The agent must infer the selection rule entirely from the tool name.

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