corpusAI Cloud Pricing

Region spot snapshot

spot_snapshot

Read-onlyIdempotent

Paid (0.10 USDC per call). Current price of every instance type, zone and product in a whole region, in one call. Bulk snapshot: the most recent event of every series in the region (about 6,000 rows for an AWS region), with timestamp and age per row. Same semantics as /spot/latest. Priced higher because one call returns the entire current price surface of the region.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	Yes	Region 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
`provider`	Yes	Cloud provider. One of `aws`, `gcp`, `azure`.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Newest event in the region; the snapshot is current to this time.
`count`	No
`prices`	No
`region`	No
`provider`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

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

First observedSep 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds meaningfully beyond that: an explicit price (0.10 USDC per call), an expected result size (~6,000 rows for an AWS region), and per-row timestamp/age contents.

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 the cost and then explains the payload, bulk size, and pricing rationale in four tight sentences. There is slight redundancy between the 'current price of every instance type' line and the 'bulk snapshot' line, but no wasted padding.

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?

For a two-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: cost, scope, result volume, and semantic equivalence to /spot/latest. Nothing material is missing.

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%, so both the region slug formats and the provider enum are already fully documented in the schema. The description adds no syntax or format detail beyond what the structured fields provide, so the baseline 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: returns the current price of every instance type, zone and product in an entire region in one call. It also names the sibling it mirrors ('same semantics as /spot/latest') and contrasts with per-series tools, so an agent can distinguish it from the other spot_* tools.

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?

It implies the usage context ('bulk snapshot', 'one call returns the entire current price surface') and notes it's priced higher, which hints at when it's worth it over targeted tools. However, it never explicitly states when to prefer it over spot_latest, spot_daily or spot_hourly, leaving the choice to inference.

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 tools Inspect

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.