Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-getBillingStatus

Read-onlyIdempotent

Retrieves the current Stripe billing status for a Dokploy instance, letting you verify subscription and payment state before managing deployments or infrastructure.

Instructions

GET /stripe.getBillingStatus

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": "stripe-getBillingStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that – no indication of account scoping, auth requirements, or what 'billing status' comprises.

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

Conciseness2/5

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

It is short, but it is under-specification rather than conciseness: a bare endpoint path that conveys no meaning an agent could not already derive from the tool name. Nothing is front-loaded because nothing informative is present.

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

Completeness2/5

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

With no output schema and no parameters, the description was the only place to explain what a billing status response conveys (plan, subscription state, limits) and it omits all of it. For a status-inspection tool against many similarly named Stripe siblings, this leaves the agent unable to choose confidently.

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?

The tool takes zero parameters, so the schema is complete and the description has no parameter semantics to compensate for. Baseline 4 applies.

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

Purpose2/5

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

The description is just the HTTP verb plus the tool name ("GET /stripe.getBillingStatus"), a tautological restatement rather than an explanation of what billing status means or contains. It gives no basis for distinguishing this from siblings such as stripe-getCurrentPlan or stripe-canCreateMoreServers.

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, no prerequisites, and no mention of alternatives. An agent must infer from the name alone whether this is a subscription check, a payment-method check, or a quota check, and how it differs from stripe-getCurrentPlan.

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