Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

Check an environment budget

get_environment_budget
Read-onlyIdempotent

Check an environment's monthly budget: the cap, what it has spent this month (UTC, GPU instances plus inference) and what is left. At 100% of the budget, launches in that environment fail, its running instances are stopped and its API keys stop serving inference until the month ends. Budgets can only be set or changed by a workspace owner or admin in the Runcrate dashboard, not from here.

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_environment_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)
environment_idNoEnvironment ID from list_environments (optional: defaults to the environment named by environment, otherwise the one this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / environment_id / description
      Previous value: -"Environment ID from list_environments (optional: defaults to the environment named by env, otherwise the one this session acts in)"New value: +"Environment ID from list_environments (optional: defaults to the environment named by environment, otherwise the one this session acts in)"
    • 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

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/non-destructive; the description goes well beyond them by explaining the operational consequence of reaching 100%: launches fail, running instances are stopped, and API keys stop serving inference until month end. It also clarifies the accounting basis (UTC, GPU instances plus inference) and who can change budgets.

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?

Three sentences, front-loaded with the purpose and return contents, followed by the behavioral consequence and the permission constraint. No redundant restatement of the title or schema, and every clause carries information an agent can act on.

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?

With no output schema, the description compensates by listing exactly what the call returns (cap, spend, remainder). For a read-only, zero-required-parameter tool with full schema coverage, nothing needed to select or invoke 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%, and each of the three optional parameters already documents its default resolution (authenticated workspace, session environment, environment_id fallback). The description adds no additional parameter-level meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Check an environment's monthly budget') and immediately enumerates what is reported: the cap, month-to-date spend (UTC, GPU instances plus inference), and remaining amount. That level of specificity lets an agent distinguish this from generic billing reads, even though no sibling is named explicitly.

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?

It gives a clear usage boundary: budgets can only be set or changed by a workspace owner or admin in the Runcrate dashboard, not from here, which prevents the agent from trying to mutate a budget. It does not explicitly route between this and the billing_balance/billing_usage siblings, leaving that inference to the agent.

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