Skip to main content
Glama
TravisLinkey

Provision Stack MCP

by TravisLinkey

pricing.get

Read-onlyIdempotent

Estimate monthly and hourly costs for a single cloud resource type (e.g., EC2, RDS, GCP Cloud Run) without provisioning. Input resource type and optional specs to get cost breakdown.

Instructions

Estimate monthly and hourly USD cost for one cloud resource type (e.g. ec2_instance, rds_instance, gcp_cloud_run) without provisioning anything. Use after suggestions.generate when the user wants a component-level breakdown for a single resource; prefer region from region.detect. Provider is inferred from resourceType prefixes (gcp_*, azure_*, oracle_*) when omitted. Do not use for full-stack option comparison — that is suggestions.generate. Does not create resources or hold credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneNoGCP/Azure availability zone when required
ocpusNoOracle OCPU count for flexible shapes
shapeNoOracle compute shape (e.g. VM.Standard.E4.Flex)
regionNoCloud region; defaults via region.detect for the provider
sizeGbNoDisk/volume size in GiB (EBS, etc.)
vmSizeNoAzure VM size (e.g. Standard_B1s)
providerNoCloud provider (auto-detected from resourceType if omitted)
storageGbNoObject/database storage size in GiB
volumeTypeNoVolume type (e.g. gp3, io2)
machineTypeNoGCP machine type (e.g. e2-medium)
memoryInGbsNoOracle memory in GiB for flexible shapes
instanceTypeNoAWS instance type (e.g. t3.micro) for compute/RDS
resourceTypeYesCloud resource type to price (prefix gcp_/azure_/oracle_ selects provider)
instanceCountNoNumber of instances to price (default 1)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYes
providerYes
componentsYes
estimateIdYes
descriptionYes
resourceTypeYes
hourlyCostUsdYes
monthlyCostUsdYes
Behavior5/5

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

Description confirms it does not create resources or hold credits, aligning with annotations readOnlyHint=true, idempotentHint=true, destructiveHint=false. It also explains provider inference from resourceType prefixes, adding behavioral context beyond annotations.

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?

Description is five sentences, front-loaded with purpose, then usage order, provider inference, exclusions, and safety confirmation. 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 the tool's complexity (14 params, 1 required), annotations, and presence of output schema, the description provides all necessary context: purpose, usage sequence, provider inference, and what it does not do. It is complete.

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?

Schema coverage is 100% with detailed descriptions for each parameter. The description adds overall usage context like provider auto-detection and region defaults, but does not elaborate on individual parameters. This is adequate given the schema richness.

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?

Description clearly states it estimates monthly/hourly USD cost for one cloud resource type. It specifies the verb 'estimate' and resource 'cloud resource type', and distinguishes from siblings like suggestions.generate by noting it's not for full-stack comparison.

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 'Use after suggestions.generate' and 'prefer region from region.detect'. It also states not to use for full-stack option comparison, naming the alternative sibling tool.

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/TravisLinkey/provision-stack-mcp'

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