Compute Screener

What changed

get_price_changes

Read-onlyIdempotent

What moved, as the site's changes show it: every listed GPU and company index's change over 1, 5, 7 or 30 days (the site's 1D, 5D, 1W and 1M), largest first, and every AI model whose price (at the mix, as its page charts it) moved over that time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_price_changes"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	How many days back: 1, 5, 7 or 30.

Output Schema

Name	Required	Description
`days`	No
`license`	No
`index_moves`	Yes
`model_price_changes`	Yes	Each model whose price at the mix (87% cache read, 12% input, 1% output) moved, as its page's chart and changes show it

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 6, 2026

addedOutput schema / properties / index_moves / items / properties / from_between

Added value: +{
+  "description": "With from_interpolated: the days before and after from_date it is taken between",
+  "items": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

changedOutput schema / properties / index_moves / items / properties / from_interpolated / description

Previous value: -"The history has no value on from_date: from_value is interpolated between the nearest values around it, as the site's changes are"New value: +"The history has no value on from_date: the change is measured from the value that day taken between the two days in from_between, as the change cell's hover says"

addedOutput schema / properties / index_moves / items / properties / from_value / description
```
Added value: +"The value on from_date (none when it is estimated)"
```

addedOutput schema / properties / model_price_changes / items / properties / from_between

Added value: +{
+  "description": "With from_interpolated: the days before and after from_date it is taken between",
+  "items": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

changedOutput schema / properties / model_price_changes / items / properties / from_interpolated / description

Previous value: -"The history has no value on from_date: from_value is interpolated between the nearest values around it, as the site's changes are"New value: +"The history has no value on from_date: the change is measured from the value that day taken between the two days in from_between, as the change cell's hover says"

addedOutput schema / properties / model_price_changes / items / properties / from_value / description
```
Added value: +"The value on from_date (none when it is estimated)"
```

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / index_moves / items / properties / from_interpolated

Added value: +{
+  "description": "The history has no value on from_date: from_value is interpolated between the nearest values around it, as the site's changes are",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / model_price_changes / items / properties / from_interpolated

Added value: +{
+  "description": "The history has no value on from_date: from_value is interpolated between the nearest values around it, as the site's changes are",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

Changed17 schema fields changedOct 28, 2026
- changedInput schema / properties / days / description
```
Previous value: -"How many days back (1 to 30)."New value: +"How many days back: 1, 5, 7 or 30."
```
- addedInput schema / properties / days / enum
```
Added value: +[
+  1,
+  5,
+  7,
+  30
+]
```
- removedInput schema / properties / days / maximum
```
Removed value: -30
```
- removedInput schema / properties / days / minimum
```
Removed value: -1
```
- addedOutput schema / properties / model_price_changes / description
```
Added value: +"Each model whose price at the mix (87% cache read, 12% input, 1% output) moved, as its page's chart and changes show it"
```
- addedOutput schema / properties / model_price_changes / items / properties / change_pct
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / model_price_changes / items / properties / date
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / model_price_changes / items / properties / from_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / model_price_changes / items / properties / from_value
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- removedOutput schema / properties / model_price_changes / items / properties / input_from
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / model_price_changes / items / properties / input_to
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / model_price_changes / items / properties / output_from
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / model_price_changes / items / properties / output_to
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / model_price_changes / items / properties / to_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / model_price_changes / items / properties / to_value
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / model_price_changes / items / properties / unit
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- changedOutput schema / properties / model_price_changes / items / required
```
Previous value: -[
-  "model",
-  "date"
-]New value: +[
+  "model"
+]
```
Changed17 schema fields changedOct 27, 2026
- changedOutput schema / properties / days / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / from_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / kind / enum
```
Previous value: -[
-  "gpu",
-  "company"
-]New value: +[
+  "gpu",
+  "company",
+  null
+]
```
- changedOutput schema / properties / index_moves / items / properties / kind / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / to_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / unit / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / index_moves / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / license / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / items / properties / company / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / items / properties / date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / items / properties / model / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / model_price_changes / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
AddedOct 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are sorted largest-first and merge three entity families (GPUs, company indices, AI models). However, vague phrases like 'at the mix, as its page charts it' and the absence of any statement about result volume or empty periods leave real ambiguity about what comes back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, so nothing is wasted, but it is dense and back-loaded with nested parentheticals ('at the mix, as its page charts it') that obscure rather than clarify. The ordering and scope facts, which matter most, are buried mid-sentence instead of front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value description is not required, and one optional enum parameter keeps the tool simple. Still, the opaque 'at the mix' clause and the lack of clarity on whether all three entity families are always returned make the definition only just adequate for an agent deciding whether to call it.

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 documents the four allowed values, so baseline is 3. The description adds a small amount by mapping 1/5/7/30 to the site's 1D/5D/1W/1M labels, but it does not explain default behavior or what the windows mean operationally, so it does not exceed the schema meaningfully.

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 the resource (every listed GPU and company index, plus AI models), the measure (change over the period) and the ordering (largest first), which is enough to distinguish this change-digest from siblings like get_price_history or get_gpu_prices. The phrasing 'What moved, as the site's changes show it' is indirect rather than a clean verb+resource statement, and it never explicitly contrasts itself with a sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite get_price_history, get_gpu_market_prices and get_model_prices all sitting nearby. An agent can infer this is a recent-changes digest, but nothing steers it away from the point-query 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?