Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Balance, usage and your prices (free)

get_balance

Read-onlyIdempotent

Retrieve account wallet balance, separate bonus and plan grants, month-to-date usage, and account-specific per-operation prices to check spend before or after paid API work.

Instructions

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.

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.

Changed6 schema fields changedv0.12.2Oct 16, 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 / grants_usd

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Addedv0.9.0Sep 24, 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 ('this call never spends credits') and, critically, the spending-order and coverage rules for grants — grants are consumed first, only on covered operation types, and never pay for phone numbers, so balance_usd + grants_usd overstates spendable funds. It also flags that returned prices are the account's real rates versus the list prices shown in other tool descriptions.

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 purpose and the free-cost caveat, then the non-obvious grant semantics. Every sentence carries information an agent would otherwise get wrong, though the grant explanation runs long and is denser than needed for a routine balance check.

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?

An output schema exists, so return-shape detail is not required, and the description still explains the two headline fields and why they cannot simply be summed. Combined with zero required params and 100% schema coverage, an agent has everything needed to invoke and interpret this correctly.

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 each of the five flags (include_usage, include_prices, include_transactions, include_token_analytics, timeout_ms) is already documented with its own meaning and default. The description conveys that usage and prices are part of the result but never maps that to the optional flags, so it adds little over the schema.

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 clause names the exact resource and the three things returned (wallet balance, month-to-date usage, account-specific per-operation prices), plus the cost property ('Free: this call never spends credits'). No sibling in the list covers account/billing state, so it is unambiguous against count_leads, health, etc.

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 (what the user can afford) and after it (what was spent)'. That is a clear when-to-use signal. It stops short of naming alternatives or stating when not to call (e.g. whether include_usage makes a separate usage tool unnecessary), so it is not a full 5.

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