Skip to main content
Glama
Sign In
monacloud-mcp

monacloud-mcp

Official
by themonagroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Danh sách service MONA Cloud

cloud_services_list

List available VPS and database services from your MONA Cloud account. Enable sandbox mode to include free trial services without requiring a wallet or additional headers.

Instructions

Liệt kê VPS/database; sandbox=true gộp cả service thử 0đ bằng API, không cần header.

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

Input Schema

NameRequiredDescriptionDefault
sandboxNosandbox=true: thử 0đ, không cần ví

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden and does add some behavior: `sandbox=true` merges trial 0đ services and 'không cần header' signals an auth-header requirement. It does not mention read-only status, pagination, or any side effects, though listing is implicitly non-destructive.

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?

A single front-loaded sentence states the action, resource, parameter mode, and header requirement without filler. Every clause earns its place.

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 low-complexity listing tool with one optional parameter and no output schema, the description covers purpose, the sandbox modality, and the header requirement. It stops short of describing the response shape or pagination, but those are minor gaps for this simple call.

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

Parameters3/5

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

Schema coverage is 100% and the only parameter (`sandbox`) already has a schema description stating 'thử 0đ, không cần ví'. The tool description repeats the sandbox behavior and adds the header note, but this is only marginal value beyond the schema.

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 ('Liệt kê') and resource ('VPS/database'), so an agent can tell this is a listing operation. It is clear but does not explicitly differentiate itself from the similarly named sibling `cloud_services` or `cloud_subscription_list`.

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 description gives useful invocation context: `sandbox=true` includes 0đ trial services and no header is required. It does not, however, state when to prefer this tool over siblings like `cloud_services` or `cloud_subscription_list`, leaving alternative selection to inference.

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