Compute Screener

Price history

get_price_history

Read-onlyIdempotent

Price history of one GPU (USD per GPU-hour) or one AI company (USD per 1M tokens), oldest first. GPU history is daily from 2025-11-07 for H100 and A100, from 2026-10-23 for the other first GPUs and from its first index day for each GPU added later, weekly before; token history is daily from 2025-01-01.

Input Schema

Name	Required	Description	Default
`days`	No	How many days back from the latest value.
`name`	Yes	A GPU or an AI company.

Output Schema

Name	Required	Description	Default
`url`	No
`kind`	Yes
`name`	Yes
`unit`	Yes
`points`	Yes
`license`	No
`sources`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / name / enum

Previous value: -[
-  "H100",
-  "H200",
-  "A100",
-  "B200",
-  "B300",
-  "RTX PRO 6000",
-  "L40S",
-  "RTX A6000",
-  "Anthropic",
-  "OpenAI",
-  "Google",
-  "xAI",
-  "Meta",
-  "Moonshot AI",
-  "Alibaba",
-  "DeepSeek",
-  "Z.ai",
-  "Xiaomi",
-  "StepFun",
-  "MiniMax",
-  "Mistral",
-  "Reflection AI",
-  "NVIDIA",
-  "Thinking Machines"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "RTX PRO 6000",
+  "L40S",
+  "RTX A6000",
+  "RTX 6000 Ada",
+  "L40",
+  "RTX 4090",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi",
+  "StepFun",
+  "MiniMax",
+  "Mistral",
+  "Reflection AI",
+  "NVIDIA",
+  "Thinking Machines"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / name / enum

Previous value: -[
-  "H100",
-  "H200",
-  "A100",
-  "B200",
-  "B300",
-  "RTX PRO 6000",
-  "Anthropic",
-  "OpenAI",
-  "Google",
-  "xAI",
-  "Meta",
-  "Moonshot AI",
-  "Alibaba",
-  "DeepSeek",
-  "Z.ai",
-  "Xiaomi",
-  "StepFun",
-  "MiniMax",
-  "Mistral",
-  "Reflection AI",
-  "NVIDIA",
-  "Thinking Machines"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "RTX PRO 6000",
+  "L40S",
+  "RTX A6000",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi",
+  "StepFun",
+  "MiniMax",
+  "Mistral",
+  "Reflection AI",
+  "NVIDIA",
+  "Thinking Machines"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / name / enum

Previous value: -[
-  "H100",
-  "H200",
-  "A100",
-  "B200",
-  "B300",
-  "MI300X",
-  "RTX PRO 6000",
-  "L40S",
-  "RTX A6000",
-  "Anthropic",
-  "OpenAI",
-  "Google",
-  "xAI",
-  "Meta",
-  "Moonshot AI",
-  "Alibaba",
-  "DeepSeek",
-  "Z.ai",
-  "Xiaomi"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "RTX PRO 6000",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi",
+  "StepFun",
+  "MiniMax",
+  "Mistral",
+  "Reflection AI",
+  "NVIDIA",
+  "Thinking Machines"
+]

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / name / enum

Previous value: -[
-  "H100",
-  "H200",
-  "A100",
-  "B200",
-  "B300",
-  "MI300X",
-  "RTX PRO 6000",
-  "Anthropic",
-  "OpenAI",
-  "Google",
-  "xAI",
-  "Meta",
-  "Moonshot AI",
-  "Alibaba",
-  "DeepSeek",
-  "Z.ai",
-  "Xiaomi"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "MI300X",
+  "RTX PRO 6000",
+  "L40S",
+  "RTX A6000",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi"
+]

Changed12 schema fields changedOct 27, 2026

changedOutput schema / properties / kind / enum

Previous value: -[
-  "gpu",
-  "company"
-]New value: +[
+  "gpu",
+  "company",
+  null
+]

changedOutput schema / properties / kind / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / license / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / name / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / points / items / properties / date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / points / items / properties / price / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
changedOutput schema / properties / points / items / properties / provisional / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```

changedOutput schema / properties / points / items / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / points / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

changedOutput schema / properties / sources / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / unit / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / url / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "kind": {
+      "enum": [
+        "gpu",
+        "company"
+      ],
+      "type": "string"
+    },
+    "license": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "points": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "provisional": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "date",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sources": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "kind",
+    "unit",
+    "points"
+  ],
+  "type": "object"
+}

First observedOct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add context — and it does: ordering (oldest first), resolution (daily vs weekly pre-cutover), and per-GPU start dates that determine what data actually comes back. It stops short of noting truncation behavior when 'days' exceeds available history.

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?

Purpose and units are front-loaded in the first clause; the second sentence carries the coverage-window detail. The date clauses are dense and arithmetically fiddly ('from 2026-10-23 for the other first GPUs'), which slightly burdens a first read, but no sentence is filler.

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 no explanation, and the description covers what the enum value means, the unit, the granularity, and the temporal extent — enough to call the tool correctly. The remaining gap is sibling selection guidance in a crowded namespace of similar price lookups.

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 coverage is 100% and the enum fully enumerates valid names, so the schema carries most of the load. The description does add real meaning by explaining that the name parameter can be either a GPU or an AI company and that the returned unit differs accordingly, but it adds nothing about the 'days' window beyond what the schema says.

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?

The description names a specific verb+resource ('price history') and scopes it to exactly one GPU or one AI company, with units given for each case (USD per GPU-hour vs USD per 1M tokens). It does not, however, differentiate itself from close siblings like get_gpu_prices, get_token_prices, or get_price_changes, so an agent must infer the boundary.

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?

Usage is only implied: the phrase 'oldest first' plus the coverage-date detail signals this is the time-series endpoint rather than a current-price endpoint. There is no explicit 'use this when you need history; use get_gpu_price_at for a single day, get_price_changes for deltas' routing, despite several near-identical siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Compute Screener 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.

Resources

Need Help?