Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-canCreateMoreServers

Read-onlyIdempotent

Checks whether the current Stripe subscription allows creating additional servers, helping prevent server creation when plan limits are reached.

Instructions

GET /stripe.canCreateMoreServers

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond the HTTP verb - it never says this is an account-level quota/limit check or what the answer implies for follow-up actions.

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

Conciseness3/5

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

It is extremely short and front-loaded, but the single line is an endpoint restatement rather than a useful purpose statement. Brevity is not a virtue when it substitutes for meaning.

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 annotations covering return values, the description should explain that the result indicates eligibility to add more servers and how to act on it. It leaves the agent guessing about both the call's semantics and its result.

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 has zero parameters, so there are no parameter semantics to document and the baseline of 4 applies. The description neither helps nor harms here because there is nothing to describe.

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 raw endpoint restatement "GET /stripe.canCreateMoreServers", which repeats the tool name without explaining in plain language what is being checked (whether the account can add more servers) or how this differs from siblings. Differentiation from tools like stripe-getBillingStatus or stripe-getCurrentPlan is left entirely to the name.

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 guidance about when to call this versus other Stripe status tools, nor any hint that it is typically a pre-flight check before server-buildServers. The agent must infer the usage context from the name 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