Skip to main content
Glama
Sign In
monacloud-mcp

monacloud-mcp

Official
by mona-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bảng giá MONA Cloud

cloud_prices
Read-onlyIdempotent

Retrieve current hourly unit prices for MONA Cloud resources so AI agents can estimate deployment costs and budgets before provisioning.

Instructions

Đọc đơn giá giờ hiện hành.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds a modest behavioral detail: it returns the currently effective hourly rates, implying the values are time-varying rather than a static catalog. It stops short of describing scope or return structure, which is acceptable given the rich annotations.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler, well matched to a no-argument lookup. It is arguably too terse to route among the several sibling pricing tools, but there is no wasted text.

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

Completeness3/5

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

For a trivial zero-parameter read, the definition is near-minimal but workable. With no output schema present, the description could have said what the hourly rates are keyed on (services, regions) and clarified the relationship to cloud_packages/vibecloud_prices, which it omits.

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 per the rubric the baseline is 4. The description does not need to explain argument semantics, and it correctly says nothing about inputs.

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 Vietnamese description 'Đọc đơn giá giờ hiện hành' states a specific verb (read) and resource (hourly unit prices), and the title 'Bảng giá MONA Cloud' confirms this is the pricing catalog. It does not, however, distinguish itself from close siblings like cloud_packages, vibecloud_prices, or vibecloud_packages, so an agent must infer the split.

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 mention of prerequisites, and no reference to the alternative pricing tools (cloud_packages, vibecloud_prices). The agent gets only the name and a one-line purpose with nothing about when this tool is the right choice.

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