Skip to main content
Glama

thanaton_get_wallet

Inspect tenant credit wallet balances in USD and credits, tier allocation, and compute boot limits to verify available capacity before running workloads.

Instructions

Inspect tenant credit wallet, balance (USD & credits), tier allocation, and compute boot limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the shape of the returned information (USD and credit balances, tier allocation, compute boot limits), which is meaningful since no output schema exists, and "Inspect" implies a non-mutating read. It does not state permission requirements, freshness/caching, or whether the wallet is scoped to the calling tenant only.

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 with no filler; the resource is named first and the enumerated return fields follow. Nothing could be removed without losing 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 no-parameter read tool with no annotations and no output schema, the description does the essential work of summarizing the returned fields, so an agent knows what a call yields. Remaining gaps (tenant scoping, whether "compute boot limits" is a static quota or a live counter, permission needs) are modest but real given the absence of structured metadata.

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?

The tool takes zero input parameters, so there is nothing for the description to disambiguate; per the baseline for 0-param tools this sits at 4. The description appropriately spends its words on what comes back rather than on nonexistent inputs.

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 ("Inspect") and a specific resource ("tenant credit wallet") and enumerates what is surfaced: USD/credit balance, tier allocation, compute boot limits. An agent can tell this is a read-only billing/quota inspection, distinct from the adjacent thanaton_list_invoices. It stops short of explicitly contrasting itself with any sibling.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative for related questions (e.g., invoice history vs. wallet balance). Usage is only implied by the phrase "Inspect tenant credit wallet," which is adequate for a zero-parameter read tool but leaves the agent to infer the trigger conditions.

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

Deploy Server

Other Tools