corpusAI Cloud Pricing

Index history

index_history

Read-onlyIdempotent

Paid (0.05 USDC per call). Daily fixings for a ticker over a date range. Quote segments start 2026-09-13. SPOT tickers reach back to the start of the spot series (AWS daily from 2022-05-31 for A100, V100, T4, A10; from 2023-07 for H100), each row carrying its data source.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD. Default: today.
`from`	No	First day, YYYY-MM-DD. Default: earliest.
`ticker`	Yes	Ticker from /index/tickers. Example: CX.H100SXM.NEO

Output Schema

TableJSON Schema

Name	Required	Description	Default
`gpu`	No
`unit`	No
`count`	No
`series`	No
`ticker`	No
`segment`	No
`methodology`	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"
+    },
+    "gpu": {
+      "type": "string"
+    },
+    "methodology": {
+      "type": "string"
+    },
+    "segment": {
+      "type": "string"
+    },
+    "series": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "day": {
+            "type": "string"
+          },
+          "hi": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "instance": {
+            "type": "string"
+          },
+          "lo": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "n": {
+            "type": "number"
+          },
+          "source": {
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds a genuinely useful trait they omit: the 0.05 USDC per-call cost and the distinct data-availability windows (quote segments from 2026-09-13, spot series back to 2022-05-31 etc.). This is meaningful behavioral context beyond the annotations.

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, then purpose, then coverage details. Dense but each clause (price, segment start, spot backfill, per-row source) carries distinct information; the coverage enumeration is slightly list-heavy but earns its place.

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 structure needn't be explained, and the description covers pricing and data-coverage windows. Complete enough for correct invocation, though it lacks explicit sibling routing.

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 ticker/from/to are already documented. The description adds only tangential range context (earliest series start) rather than clarifying parameter syntax or formats. Baseline 3 is appropriate.

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 verb+resource: 'Daily fixings for a ticker over a date range.' The 'over a date range' phrasing distinguishes it from the single-fixing siblings like index_fixing, though no sibling is named explicitly.

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?

Conveys context (date range, paid per call) that implies when to use it, but never states when to prefer it over index_fixing, index_board, or spot_daily, nor any exclusions. Usage is inferred rather than guided.

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.