corpusAI Cloud Pricing

Data catalog

catalog

Read-onlyIdempotent

Free. Providers, regions, coverage window and event counts. One row per (provider, region) with raw-event coverage (instance types, events, first/last event) and legacy-history coverage (daily and monthly date ranges), plus sources, the legend explaining every source value returned by /spot/daily and /spot/monthly. Use the region values here verbatim in every other call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`regions`	No
`sources`	No	Legend: source value → what it is and how much to trust it.
`price_usdc`	No	Base price of one paid call (events, hourly, latest, eviction).
`prices_usdc`	No	Price per operation family: events, hourly, latest, eviction, daily, monthly, snapshot.
`generated_at`	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": {
+    "generated_at": {
+      "type": "string"
+    },
+    "price_usdc": {
+      "description": "Base price of one paid call (events, hourly, latest, eviction).",
+      "type": "string"
+    },
+    "prices_usdc": {
+      "additionalProperties": true,
+      "description": "Price per operation family: events, hourly, latest, eviction, daily, monthly, snapshot.",
+      "properties": {},
+      "type": "object"
+    },
+    "regions": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "events": {
+            "type": "number"
+          },
+          "first_event": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "history_daily_from": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "history_daily_to": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "history_instances": {
+            "description": "Types with legacy history rows.",
+            "type": "number"
+          },
+          "history_monthly_from": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "history_monthly_to": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "instances": {
+            "description": "Types with raw events.",
+            "type": "number"
+          },
+          "last_event": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ondemand": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "description": "On-demand series coverage (types, change points, from, to) or null.",
+                "properties": {
+                  "from": {
+                    "type": "string"
+                  },
+                  "points": {
+                    "type": "number"
+                  },
+                  "to": {
+                    "type": "string"
+                  },
+                  "types": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "On-demand series coverage (types, change points, from, to) or null."
+          },
+          "provider": {
+            "type": "string"
+          },
+          "region": {
+            "description": "Slug to pass as `region`.",
+            "type": "string"
+          },
+          "reserved": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "description": "AWS reserved-instance series coverage or null.",
+                "properties": {
+                  "from": {
+                    "type": "string"
+                  },
+                  "points": {
+                    "type": "number"
+                  },
+                  "to": {
+                    "type": "string"
+                  },
+                  "types": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "AWS reserved-instance series coverage or null."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sources": {
+      "additionalProperties": true,
+      "description": "Legend: source value → what it is and how much to trust it.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.3/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 value beyond that: it is 'Free' (cost/rate context not in annotations) and it doubles as the legend for `source` values used by /spot/daily and /spot/monthly, which is non-obvious cross-tool behavior.

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?

It is front-loaded with the cost ('Free') and the resource, then the row structure, then the cross-tool usage constraint. Dense but largely earned; the parenthetical lists (instance types, events, first/last event, daily/monthly ranges) are slightly heavy for a single paragraph.

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?

An output schema exists, so return values need not be spelled out, yet the description still orients the agent on how to use the result (region values reused verbatim, sources legend). Given the zero-parameter surface and rich annotations, this is essentially 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?

The tool takes zero parameters, so the baseline is 4. The description has no parameters to clarify and correctly focuses on output content and cross-tool region reuse instead.

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?

The description names the resource (a per-(provider, region) catalog of providers, regions, coverage windows and event counts) and precisely enumerates what each row contains. It also states its unique role relative to siblings: the authoritative source of `region` values and of the `sources` legend for /spot/daily and /spot/monthly.

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

Usage Guidelines4/5

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

It clearly tells the agent when to use it — call this first to obtain `region` values, which must be reused verbatim in every other call. It doesn't state explicit exclusions or name sibling alternatives by name, but the directional guidance ('use verbatim in every other call') is concrete and actionable.

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.