Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

Check balance and runway

billing_balance
Read-onlyIdempotent

Get the workspace balance and how long it lasts: creditsBalance, activeUsageCost, floating_balance_usd (the balance net of what running instances have used so far, in USD), burn_usd_per_hour (what the running instances cost together) and runway_hours (hours the floating balance lasts at that rate; null when nothing runs), which says how soon the balance needs topping up before running work runs out of credit.

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

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / env
      Removed value: -{
-  "description": "Environment name (optional — defaults to main)",
-  "type": "string"
-}
    • addedInput schema / properties / environment
      Added value: +{
+  "description": "Environment name (optional: defaults to the environment this session acts in)",
+  "type": "string"
+}
    • changedInput schema / properties / workspace / description
      Previous value: -"Workspace ID (optional — defaults to authenticated workspace)"New value: +"Workspace ID (optional: defaults to the authenticated workspace)"
  2. 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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real semantics beyond them: floating_balance_usd is net of what running instances have consumed, and runway_hours is null when nothing runs — an edge case an agent would otherwise misread as an error.

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?

It is a single front-loaded sentence that puts the resource and purpose first, and every clause about a returned field earns its place. It is dense with stacked parentheticals, which slightly hurts scanability but not accuracy.

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, and the description compensates by naming and defining each returned field, including the null-runway case, which is exactly the completeness burden this tool carries. With only two optional, fully documented parameters and standard read-only annotations, nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%; both optional parameters are fully documented in the schema as defaulting to the authenticated workspace and the current session environment. The description adds no extra meaning about workspace or environment scoping, so the baseline 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 opens with a specific verb+resource ("Get the workspace balance and how long it lasts") and then enumerates the exact return fields, so it is clearly a point-in-time balance/runway read rather than a usage-history or top-up tool. It does not name a sibling like billing_usage or get_auto_recharge to draw the boundary explicitly, which keeps it off a 5.

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?

Usage is only implied through the phrase "how soon the balance needs topping up before running work runs out of credit," which hints at pre-launch and monitoring checks. There is no explicit when-to-use, when-not-to-use, or pointer to billing_usage / get_auto_recharge / top_up as the alternatives.

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

All Runcrate 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