Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

get_ai_spend

Read-only

AI usage spend grouped by model: calls, AI seconds, tokens, and amount (minor units). Defaults to month-to-date.

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": {
      "purpose": "<purpose>"
    },
    "name": "get_ai_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRFC3339 window end; defaults to now
fromNoRFC3339 window start; defaults to the first of this month
purposeYesRequired 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavior beyond that: results are aggregated per model, the specific counters returned, that amount is in minor units, and that the default window is month-to-date.

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?

A single front-loaded sentence that names the resource, grouping, metrics, unit convention, and default window with no filler. Every clause carries information.

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 simple read-only aggregate with full schema coverage and no output schema, this is close to sufficient: it names what is returned and the unit of the monetary figure. It stops short of saying which currency minor units refer to or whether the grouping can be widened, which a caller might wonder about.

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%, so from/to and the purpose parameter are already documented, making 3 the baseline. The description's "defaults to month-to-date" essentially restates the schema defaults for from/to and adds no format or constraint detail beyond them.

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 resource (AI usage spend) and the grouping dimension (by model), plus the metrics returned (calls, AI seconds, tokens, amount). This separates it from the balance/history siblings like get_wallet_balance and list_wallet_statements, though it never names an alternative explicitly.

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?

"Defaults to month-to-date" gives a usable time-window convention and the grouping implies the reporting use case. However, there is no explicit statement of when to pick this over get_call_stats, get_wallet_balance, or list_wallet_statements, so routing is left to inference.

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