Skip to main content
Glama
x7even

OpenCloudCosts MCP

by x7even
OverviewSchemaRelated ServersScoreDiscussions
Go
Hybrid

estimate_bom

Estimate total monthly or annual cost for a multi-resource cloud stack including compute, storage, database, and AI from AWS, GCP, and Azure. Identify hidden costs like egress and load balancers.

Instructions

Use this tool for total infrastructure cost, TCO, monthly spend for a multi-resource stack, or cost comparison between architectures.

Handles compute + storage + database + AI together in a single call — do NOT call get_price individually for multi-resource questions; use this tool instead.

Returns per-item and total monthly/annual costs with real public pricing data, plus a not_included list of hidden costs (egress, load balancers, NAT Gateway, monitoring, backups). IMPORTANT: if not_included is present in the response, you MUST call get_price for each listed item — using the exact command in each item's how_to_price field — before writing your final answer. Do NOT estimate or guess any cost from the not_included list.

Each item should be a PricingSpec dict PLUS a quantity field:

  • provider: "aws" | "gcp" | "azure"

  • domain: "compute" | "storage" | "database" | "ai" | ...

  • region: region code

  • quantity: number of units (default 1)

  • hours_per_month: hours/month for compute (default 730 = always-on)

  • description: optional label for this line item Plus domain-specific fields (see get_price or describe_catalog for details).

Examples: Compute + database + storage on AWS: [ {"provider": "aws", "domain": "compute", "resource_type": "m5.xlarge", "region": "us-east-1", "quantity": 3}, {"provider": "aws", "domain": "database", "service": "rds", "resource_type": "db.r6g.large", "engine": "MySQL", "deployment": "single-az", "region": "us-east-1"}, {"provider": "aws", "domain": "storage", "storage_type": "gp3", "size_gb": 500, "region": "us-east-1"} ]

Mixed cloud: [ {"provider": "gcp", "domain": "compute", "resource_type": "n1-standard-4", "region": "us-central1", "quantity": 2}, {"provider": "azure", "domain": "compute", "resource_type": "Standard_D4s_v3", "region": "eastus", "quantity": 1} ]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A5/5.0
Behavior5/5

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

No annotations provided, but description fully discloses behavior: returns per-item and total costs, real public pricing data, and a not_included list. Also explains input format requirements.

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?

Well-structured, front-loaded with purpose and guidelines, then behavioral notes, then parameter format, then examples. Every sentence adds value; no wasted words.

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

Completeness5/5

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

Given complexity of multi-resource estimation, description covers input format, output structure, required follow-up actions, and examples. No gaps.

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

Parameters5/5

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

Schema has 0% coverage, but description completely compensates by detailing the structure of items: PricingSpec dict with provider, domain, region, quantity, hours_per_month, etc., and provides examples.

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?

Clearly states it computes total infrastructure cost, TCO, monthly spend for multi-resource stacks. Distinguishes from get_price by explicitly saying not to use get_price for multi-resource questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (multi-resource stack, cost comparison) and when not to (avoid get_price individually). Also gives important post-call instructions for not_included items.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x7even/cloudcostsmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server