Skip to main content
Glama

stripe_get_account

Retrieve the Stripe account behind your gateway to check country, default currency, charges and payouts status, submitted details, and outstanding requirements.

Instructions

The Stripe account behind the gateway: country, default currency, charges/payouts enabled, details submitted, requirements (currently_due, past_due, disabled_reason).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "stripe_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the returned content (country, currency, capability flags, details_submitted, and the requirements sub-fields currently_due/past_due/disabled_reason), which compensates for the missing output schema. It says nothing about auth requirements, whether this hits the live Stripe API, error behavior when the site has no connected account, or rate limits — so a read-only, side-effect-free profile is only implied by the noun phrasing.

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?

One dense sentence, front-loaded with the resource identity and followed by the field list; no filler or repetition. It is a sentence fragment rather than a complete statement, which slightly blunts readability but wastes no tokens.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no annotations and no output schema, the description does the essential work by enumerating the returned fields, including the nested requirements keys. What is missing — auth/connection prerequisites and failure modes — is modest for a low-risk getter but would matter if the site has no Stripe account connected.

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?

There is a single required parameter (site) and schema description coverage is 100%, with the schema itself pointing to list_sites. The description adds no meaning about the site parameter, but per the baseline rule for high-coverage schemas, 3 is the ceiling-appropriate score.

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

Purpose4/5

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

The description names a specific resource — the Stripe account behind the gateway — and enumerates exactly what it exposes (country, default currency, charges/payouts enabled, details submitted, requirements). That is enough for an agent to know this is a read of account-level status rather than charges, refunds or webhooks. It loses a point for not distinguishing itself from close siblings such as stripe_get_settings or woo_helper_stripe_status, which the agent must infer on its own.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of what question this tool answers, no prerequisites, and no pointer to an alternative like stripe_get_settings. The only usage signal is implicitly conveyed by the field list. An agent must guess the selection criteria from sibling names alone.

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

Deploy Server

Other Tools