Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-getCurrentPlan

Read-onlyIdempotent

Retrieve the active Stripe plan for your Dokploy account to check subscription tier and billing status.

Instructions

GET /stripe.getCurrentPlan

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-getCurrentPlan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 structurally. The description contributes nothing beyond that: no note on what 'current plan' means when no subscription exists, no partial-failure or empty-result behavior, and no auth context.

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 shortness here reflects under-specification rather than efficiency. A single endpoint stub carries no useful signal and is not front-loaded toward an agent's decision.

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

Completeness1/5

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

With no output schema, the description is the only place the return value (plan name, price, limits?) could be described, and it says nothing. For a zero-arg tool whose entire value is its response shape, this is inadequate.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema is self-explanatory.

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 only restates the tool name as an HTTP path ("GET /stripe.getCurrentPlan"). It implies a read of the current Stripe plan, but adds no resource scope, no data fields, and nothing that distinguishes it from siblings like stripe-getBillingStatus or stripe-getProducts.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever, no prerequisites (e.g. whether a Stripe customer/subscription must exist), and no mention of alternatives. An agent must guess between this and the other stripe-get* tools.

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