Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-isUserSubscribed

Read-onlyIdempotent

Checks whether the authenticated user has an active subscription and returns the status for access or feature gating.

Instructions

GET /settings.isUserSubscribed

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": "settings-isUserSubscribed"
  }
}

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 by structured data. The description adds nothing beyond that — no mention of auth requirements, whether the result is caller-scoped, or what the response shape is. It does not contradict the annotations.

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 a single token-efficient line, but brevity here comes from under-specification rather than discipline. The only content is the verb and path, which the tool name already conveys, so it earns little of its space.

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, the description is the only place to say what an isUserSubscribed call yields (presumably a boolean plus plan details) and whose subscription it reports. It says none of that, leaving a simple read tool unnecessarily opaque.

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 schema accepts zero parameters, so there is no parameter semantics to explain; the baseline for a no-param tool applies. Nothing in the description misleads about inputs.

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 path 'GET /settings.isUserSubscribed', which restates the tool name rather than explaining the operation. It implies a read of the caller's subscription status, but never states what 'subscribed' means (plan, license, trial) or what is returned.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives such as settings-isCloud, despite many settings-* siblings that could plausibly answer adjacent questions. The agent must infer everything from the name.

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