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

Check your account balance, month-to-date usage, and actual per-operation prices for free. Use it before paid work to budget and after to report spending accurately.

Instructions

Account balance, month-to-date usage and THIS account's real 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. Report both figures; do not add them up as what the user can spend. Call it before a batch of paid work (so you can tell the user what they can afford) and after (so you can report exactly what was spent). The prices it returns beat any number in a tool description — those are list prices.

Input Schema

TableJSON 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

TableJSON 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.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds non-obvious behavior: the call is free and never spends credits, grants are spent before balance but only on covered operations (a perk never pays for phone numbers), and balance_usd and grants_usd must not be summed. It also establishes authority — the returned prices override list prices 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?

The purpose and the free-call guarantee are front-loaded, and each subsequent sentence carries non-obvious guidance (grant spending order, do not sum, when to call). It runs several sentences long for a getter and could be tightened, but no sentence is filler.

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 raw return values need not be enumerated, yet the description still explains the two headline figures and how to interpret them together — exactly the ambiguity an agent would hit. Combined with the free-call and pricing-authority notes, nothing needed 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%, so the schema already documents timeout_ms, include_usage, include_prices, include_transactions and include_token_analytics including defaults and free/paid status. The description adds no input-parameter detail beyond that, so the baseline 3 applies even though the output-field semantics it explains are valuable.

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 names specific resources — account balance, month-to-date usage, and this account's real per-operation prices — with a clear verb framing. None of the siblings (search/enrich/count/bulk/webhook tools) overlap this function, so the agent can tell immediately what it retrieves and that it is a read-only account-status call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Timing is stated explicitly: call it before a batch of paid work to tell the user what they can afford, and after to report what was spent. This is a concrete when-to-use pattern with a stated purpose for each occasion, leaving nothing to inference for the agent's workflow.

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

Deploy Server