corpusAI Cloud Pricing

Region on-demand snapshot

ondemand_snapshot

Read-onlyIdempotent

Paid (0.10 USDC per call). Current on-demand list price of every instance type in a 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	Default
`note`	No
`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": {
+    "count": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    },
+    "prices": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "instance": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "since": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds the important behavioral trait that the call is paid (0.10 USDC per call), which is not covered by annotations, though payment mechanics and rate limits remain unspecified.

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?

Two short sentences, front-loading the paid cost followed by the exact purpose. No wasted words and the key information is immediately visible.

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?

For a simple two-parameter read-only snapshot with an output schema and rich annotations, the description covers purpose and cost adequately. The main gap is sibling routing among the many pricing snapshot tools, which keeps it from being fully complete.

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 both required parameters are fully documented in the schema. The description adds no syntax, enum, or format details beyond what the schema already provides, so baseline 3 applies.

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 (current on-demand list price) and scope (every instance type in a region). Clear what it returns, but does not differentiate itself from sibling pricing tools such as ondemand, reserved_snapshot, or spot_snapshot.

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 guidance on when to use this tool versus alternatives like ondemand or reserved_snapshot. The paid cost is stated, but there are no prerequisites, exclusions, or routing cues for an agent choosing among many siblings.

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.