Skip to main content
Glama

Account Balance

varity_balance
Read-onlyIdempotent

Check available, app-reserved, and owed USD amounts before deploying or when you need to know how much balance remains.

Instructions

Read your Varity balance in USD: available, set aside for running apps, and owed. reserved_usd is the amount set aside for the user's running apps (their monthly maximums), not a measure of funded backing. The data carries exact decimal USD strings; the message rounds to cents. Use before deploying or when asked how much balance remains. An unavailable read is never reported as zero.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior the annotations cannot convey: that reserved_usd is not funded backing, that values arrive as exact decimal strings while the message rounds to cents, and critically that an unavailable read is never silently reported as zero. That last point discloses a failure-mode guarantee an agent would otherwise misread as a real balance of $0.

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 sentences, front-loaded with the readable purpose and balance components before the clarifications. Every sentence carries weight, though the reserved_usd caveat is dense enough that a reader must slow down mid-paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey the return shape, and it does: three named components, exact decimal strings versus cents-rounded message text, plus the zero-versus-unavailable distinction. For a zero-parameter read tool, an agent has everything needed to call it and interpret the result.

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 parameters, so the baseline is 4. The description's discussion of reserved_usd explains a response field rather than an input, which is useful but does not change the fact that there is no input surface to clarify.

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?

Opens with a specific verb and resource ("Read your Varity balance in USD") and enumerates the three components returned: available, set aside for running apps, and owed. No sibling tool covers account balance, so the purpose is unambiguous even without naming an alternative.

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?

"Use before deploying or when asked how much balance remains" gives two concrete triggering situations. It stops short of stating when not to use it or pointing to a related sibling like varity_cost_calculator for pre-deploy estimates, which keeps it at a solid 4 rather than a 5.

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