Generect

Balance, usage and your prices (free)

get_balance

Read-onlyIdempotent

Account balance, month-to-date usage and this account's own per-operation prices. Free: this call never spends credits. balance_usd is the wallet; grants_usd is bonus and plan credit (sign-up bonus, perks, plan allowance), reported apart. Grants are spent first, but only on the operations each one covers: a promo perk or a plan allowance may not pay for API calls, and a perk never pays for phone numbers, so the two figures do not add up to what the account can spend. Useful before a batch of paid work (what the user can afford) and after it (what was spent). These are the account's real rates; prices in tool descriptions are list prices.

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

Input Schema

Name	Required	Description
`timeout_ms`	No	Request timeout in milliseconds.
`include_usage`	No	Also return the month-to-date credit usage broken down by operation type. Free.
`include_prices`	No	Include this account's per-operation prices. Default true.
`include_transactions`	No	Also return the N most recent transactions (each shows the operation type and dollar amount).
`include_token_analytics`	No	Also return per-API-token request counts for the last 30 days (by endpoint and status). Free. Useful for answering "which integration is making these calls?".

Output Schema

Name	Required	Description	Default
`cost`	No
`email`	No
`usage`	No
`test_mode`	No
`grants_usd`	No
`balance_usd`	No
`preview_tier`	No
`prices_source`	No
`token_analytics`	No
`your_prices_usd`	No
`test_mode_notice`	No
`recent_transactions`	No
`used_this_month_usd`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026
- addedOutput schema / properties / grants_usd
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

Changed5 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Changed3 schema fields changedSep 24, 2026

addedInput schema / properties / include_token_analytics

Added value: +{
+  "description": "Also return per-API-token request counts for the last 30 days (by endpoint and status). Free. Useful for answering \"which integration is making these calls?\".",
+  "type": "boolean"
+}

addedInput schema / properties / include_usage

Added value: +{
+  "description": "Also return the month-to-date credit usage broken down by operation type. Free.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "balance_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "email": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "preview_tier": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "prices_source": {
+      "type": "string"
+    },
+    "recent_transactions": {},
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "token_analytics": {},
+    "usage": {},
+    "used_this_month_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    },
+    "your_prices_usd": {}
+  },
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses cost behavior that matters operationally: the call is free and never spends credits, grants are consumed before wallet balance, and grants only cover certain operation types (a perk never pays for phone numbers). It also warns that balance_usd and grants_usd do not sum to spendable funds, which directly prevents a downstream misinterpretation.

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?

Front-loaded with what is returned, then progressively narrows to cost semantics and usage timing; every sentence carries distinct information. The grants paragraph is slightly winding and could be tightened, but nothing is pure repetition.

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?

For a read-only, zero-required-parameter introspection call with a full output schema, the description covers what an agent needs: what comes back, that it is free, how the two money figures relate, and when to call it. Return-value detail is correctly left to the output schema.

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%, so all five optional flags are already documented. The description only implicitly maps to include_usage and include_prices through its phrasing and adds no syntax, defaults, or interaction details beyond the schema, 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 opening sentence names the exact resource set: account balance, month-to-date usage, and this account's own per-operation prices. It also states a distinguishing scope (real account rates vs. list prices elsewhere), so an agent can tell at a glance this is the billing/credits introspection tool rather than an enrichment or search tool.

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 concrete usage contexts: before a batch of paid work to see what the user can afford, and after it to see what was spent. It does not name any alternative tool or an explicit case for not calling it, which keeps it below a 5.

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

All Generect tools Inspect

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.