Skip to main content
Glama

corpusAI Cloud Pricing

by io.github.JTraversa
OverviewDiscussionsAdmin

Current spot price per zone

spot_latest
Read-onlyIdempotent

Paid (0.01 USDC per call). Price currently in force per zone and product for one instance type. The most recent event of every (zone, product) series of the type, with its timestamp and age. A price is only meaningful while the provider still offers the type; AWS series older than ~10 days are likely retired, GCP/Azure reprice rarely so old timestamps are normal. For every type in a region at once use /spot/snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1
instanceYesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerYesCloud provider. One of `aws`, `gcp`, `azure`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoNewest event in the region; the snapshot is current to this time.
countNo
pricesNo
regionNo
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "as_of": {
+      "description": "Newest event in the region; the snapshot is current to this time.",
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "prices": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "age_seconds": {
+            "description": "Seconds since `since`, at response time.",
+            "type": "number"
+          },
+          "az": {
+            "type": "string"
+          },
+          "instance": {
+            "type": "string"
+          },
+          "price": {
+            "description": "USD per hour.",
+            "type": "number"
+          },
+          "product": {
+            "type": "string"
+          },
+          "since": {
+            "description": "When this price took effect.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new context: a per-call charge (0.01 USDC) and the staleness/retirement semantics of the returned data. It stops short of describing pagination or response shape, but the cost disclosure and freshness caveats are material behavioral context.

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?

Front-loads cost and the core definition, then freshness caveats, then the routing pointer to the sibling. Every sentence is substantive, though the provider-specific retirement aside is slightly dense and could be tightened.

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?

An output schema exists, so return values need not be explained; the description still covers cost, what each record represents, freshness interpretation, and the alternative tool. An agent has everything needed to call it correctly.

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 100% and all three params (provider, region, instance) are documented in the schema with examples and an enum. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.

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?

Specific verb+resource: it returns the currently-in-force spot price per (zone, product) for a single instance type, described as the most recent event of each series. It explicitly names the sibling it is not (/spot/snapshot) so the agent can distinguish them without opening schemas.

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?

Gives an explicit alternative and the condition that selects it: 'For every type in a region at once use /spot/snapshot.' It also tells the agent how to interpret stale timestamps per provider (AWS ~10 days likely retired, GCP/Azure rarely reprice), which is when-to-trust guidance a caller needs.

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

All corpusAI Cloud Pricing toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources