Skip to main content
Glama
cloudprice-mcp

cloudprice-mcp

compare_postgres_database

Compare managed PostgreSQL pricing across AWS RDS, Azure, GCP, and OCI by vCPU, memory, and storage; select a matching SKU and total compute plus storage costs.

Instructions

Compare managed PostgreSQL pricing across AWS RDS, Azure Database for PostgreSQL, GCP Cloud SQL, and OCI Database with PostgreSQL. Each request specifies vCPUs, memory, and storage_gb; the tool picks the cheapest matching SKU per cloud and totals compute + storage. Prices are hand-entered estimates (as of 2026-05-04), not part of the weekly refresh — verify against the provider's page before deciding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "databases": "<databases>"
    },
    "name": "compare_postgres_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
databasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose non-obvious behavior: cheapest-matching-SKU selection per cloud, compute+storage totaling, and that prices are hand-entered as of 2026-05-04 and excluded from the weekly refresh. It omits region/currency assumptions and any indication of what the response contains, which is significant for a pricing tool.

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?

Two tight sentences: scope first, mechanics second, caveat last. No filler or repetition, though the mid-sentence schema recap ('Each request specifies vCPUs, memory, and storage_gb') could be trimmed since it partly restates the input shape.

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 single-parameter, nested-array tool with no output schema, the description conveys enough to call it correctly: what inputs drive matching, how totals are formed, and a data-freshness warning. Remaining gaps (region, currency, response shape, handling of quantity/hours) are real but secondary.

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 description coverage is reported at 0%, so the description must compensate. It explains the core matching semantics (vcpus + memory_gb + storage_gb determine which SKU is chosen) which is genuinely valuable, but quantity (default 1), hours_per_month (default 730), and tier are left entirely unexplained, and it implies storage_gb is always supplied even though it defaults to 0.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Compare) plus the exact resource (managed PostgreSQL pricing) and enumerates the four providers/SKUs covered (AWS RDS, Azure Database for PostgreSQL, GCP Cloud SQL, OCI). An agent can distinguish this from siblings like compare_clouds or compare_object_storage on scope alone.

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?

Usage is implied by the stated scope (multi-cloud managed Postgres price comparison), and the closing caveat routes the agent to provider pages for authoritative numbers, but it never names a sibling alternative (e.g., get_aws_price for single-cloud detail or compare_clouds for broader scope) or states when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.