stripe_get_balanceGet the current Stripe account balance.
| Name | Required | Description | Default |
|---|---|---|---|
| _apiKey | Yes | Stripe secret or restricted API key (sk_...) |
| Name | Required | Description | Default |
|---|---|---|---|
| object | No | Object type (balance) | |
| pending | No | Pending balance by currency | |
| livemode | No | Live mode | |
| available | No | Available balance by currency | |
| connect_reserved | No | Connect reserved balance by currency |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "available": {
+ "description": "Available balance by currency",
+ "items": {
+ "properties": {
+ "amount": {
+ "description": "Amount in cents",
+ "type": "integer"
+ },
+ "currency": {
+ "description": "Currency code",
+ "type": "string"
+ },
+ "source_types": {
+ "description": "Balance by source type",
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "connect_reserved": {
+ "description": "Connect reserved balance by currency",
+ "items": {
+ "properties": {
+ "amount": {
+ "description": "Amount in cents",
+ "type": "integer"
+ },
+ "currency": {
+ "description": "Currency code",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "livemode": {
+ "description": "Live mode",
+ "type": "boolean"
+ },
+ "object": {
+ "description": "Object type (balance)",
+ "type": "string"
+ },
+ "pending": {
+ "description": "Pending balance by currency",
+ "items": {
+ "properties": {
+ "amount": {
+ "description": "Amount in cents",
+ "type": "integer"
+ },
+ "currency": {
+ "description": "Currency code",
+ "type": "string"
+ },
+ "source_types": {
+ "description": "Pending balance by source type",
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-stripe_connect-api-key"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no additional behavioral context beyond restating the purpose, thus providing no extra value over the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with the key action, concise, and no extraneous text. Ideal for a straightforward tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity (one parameter, no nested objects, output schema present) and rich annotations, the description is adequately complete for an agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single parameter (_apiKey) fully described in the schema. The description does not reference parameters, but the baseline of 3 is appropriate since the schema handles the documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'current Stripe account balance', which is specific and distinct from sibling tools like stripe_get_customer or stripe_list_charges.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. However, the simplicity and uniqueness of the tool (only one parameter, retrieving a single value) reduces the need for extensive disambiguation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set has several near-duplicate entry points: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, while ask_pipeworx_grounded/deep_research and bet_research/polymarket_edges overlap heavily. Verbose descriptions help in isolation, but an agent must choose between many similar-looking research and prediction-market tools before it can act.
Naming mixes bare verbs (remember, forget, subscribe), prefixed families (pipeworx_*, polymarket_*, stripe_*), and descriptive noun-style names (entity_profile, validate_claim) with no single verb_noun pattern. Each cluster is internally consistent, but the overall set is unpredictable.
37 tools is excessive for a server named Stripe_connect, especially since only 6 tools are actually Stripe-related and the rest are a sprawling Pipeworx data-research and prediction-market stack. The count would be heavy even for the broad research domain, and it is a serious scope mismatch for the stated name.
For the Stripe domain implied by the server name, the surface is severely incomplete: it is read-only (get/list) with no way to create customers, take payments, issue refunds, update invoices, or manage subscription lifecycles. The non-Stripe research tools are broad, but that does not fill the payment workflow gap.