Skip to main content
Glama

payments_status

Read-onlyIdempotent

Get the caller's Stripe Connect status: connected, onboarded, charges_enabled, payouts_enabled, details_submitted. Per-account (not per-project). refresh=true forces a live Stripe API lookup (otherwise returns the last-cached DB state).

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": "payments_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoIf true, re-query Stripe. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral context: results are normally served from a cached DB state and can be stale unless refresh is set. It also clarifies account-level scoping, which matters for a Stripe Connect tool. Minor gaps remain (no mention of auth requirements or what an unconnected account returns), but the caching disclosure is the most valuable trait an agent needs here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the highest-value routing fact (per-account scope) and the strongest behavioral caveat (cache vs live) both stated directly. Every clause carries information.

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 zero-required-parameter, single-boolean tool with no output schema, the description does the important compensating work by naming the fields returned (connected, onboarded, charges_enabled, payouts_enabled, details_submitted) and explaining the caching model. It stops short of describing the response structure or error/edge states, which is acceptable but not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema's terse 'If true, re-query Stripe' by explaining the consequence of the default path, namely that a stale last-cached DB state is returned. That is meaningful semantic information the agent could not derive from the property description alone.

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 uses a specific verb and resource ('Get the caller's Stripe Connect status') and enumerates the returned fields, so the agent knows exactly what data comes back. It also disambiguates scope with 'Per-account (not per-project)'. It does not reference any sibling such as payments_checkout or payments_events, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

The one real guideline is 'refresh=true forces a live Stripe API lookup (otherwise returns the last-cached DB state)', which tells the agent the cached-vs-live tradeoff and implies when to set refresh. Beyond that there is no statement of when this tool should be chosen over Stripe-related siblings, and no exclusions or preconditions (e.g. what happens if the account is not connected).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources