corpusAI Cloud Pricing

Hourly spot bars

spot_hourly

Read-onlyIdempotent

Paid (0.01 USDC per call). Hourly time-weighted OHLC bars for one instance type. Per-zone series are bucketed by UTC hour with time weighting (a price counts for as long as it was in force), then collapsed across zones: open/close/avg are the median across zones, high is the max, low is the min. Window is capped at 366 days.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End of the window (exclusive), ISO 8601 UTC. Default: now.
`from`	No	Start of the window (inclusive), ISO 8601 UTC. Default: 30 days before `to`.
`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
`instance`	Yes	Instance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
`provider`	Yes	Cloud provider. One of `aws`, `gcp`, `azure`.

Output Schema

TableJSON Schema

Name	Required	Description
`to`	No
`bars`	No
`from`	No
`count`	No
`zones`	No	Number of zone series collapsed.
`region`	No
`instance`	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": {
+    "bars": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "avg": {
+            "description": "Time-weighted average price over the bucket (median across AZs). This is the value the public dashboard shows.",
+            "type": "number"
+          },
+          "close": {
+            "description": "Price in force at the end of the bucket (median across AZs).",
+            "type": "number"
+          },
+          "dur": {
+            "description": "Seconds of the bucket covered by known prices (a partial value means the series starts or ends inside the bucket).",
+            "type": "number"
+          },
+          "high": {
+            "description": "Highest price seen in any AZ during the bucket.",
+            "type": "number"
+          },
+          "hour": {
+            "description": "Bucket start, ISO 8601 UTC hour.",
+            "type": "string"
+          },
+          "low": {
+            "description": "Lowest price seen in any AZ during the bucket.",
+            "type": "number"
+          },
+          "open": {
+            "description": "Price in force at the start of the bucket, USD per hour (median across AZs).",
+            "type": "number"
+          }
+        },
+        "required": [
+          "hour",
+          "open",
+          "high",
+          "low",
+          "close",
+          "avg"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    },
+    "from": {
+      "type": "string"
+    },
+    "instance": {
+      "type": "string"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    },
+    "to": {
+      "type": "string"
+    },
+    "zones": {
+      "description": "Number of zone series collapsed.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description adds valuable context beyond annotations: a per-call cost (0.01 USDC), time-weighting semantics, the cross-zone aggregation rules for open/close/avg/high/low, and a hard 366-day window cap.

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?

The four sentences are dense but each earns its place: pricing, resource definition, aggregation logic, and window cap. The aggregation sentence is long but necessary for interpreting the OHLC bars correctly.

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?

With a full output schema and rich parameter descriptions, return values need not be explained. The description is nearly complete, covering cost, semantics, and limits, though it does not explain pagination or output ordering if any.

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 description coverage is 100%, so the baseline is 3. The description adds a meaningful constraint beyond the schema by disclosing the 366-day maximum window, which directly affects the `from` and `to` parameters and is not stated in the schema.

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

Purpose4/5

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

States a specific resource and granularity: 'Hourly time-weighted OHLC bars for one instance type.' The word 'Hourly' implicitly distinguishes it from siblings like spot_daily and spot_monthly, but it does not explicitly name or compare against those alternatives.

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

Usage Guidelines2/5

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

No explicit guidance on when to choose this tool over spot_daily, spot_monthly, spot_latest, or spot_snapshot. The hourly granularity implies a use case, but the description never states when hourly bars are appropriate or what alternatives exist.

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.