Compute Screener

Data freshness and sources

get_data_status

Read-onlyIdempotent

How fresh the data is, as the status page shows it: when the GPU and token indices were last calculated, today's index day, each GPU price source's status and last read, each GPU index's status, provider count and imputed share, and the latest days with a manifest.

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_data_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`verifier`	No
`gpu_index`	Yes
`manifests`	No
`methodology`	No
`token_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- addedOutput schema / properties / gpu_index / properties / sources / items / properties / read_every
```
Added value: +{
+  "description": "As the status page's Read every column shows it",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedOct 28, 2026

removedOutput schema / properties / gpu_index / properties / gpus / items / properties / flags

Removed value: -{
-  "items": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "type": [
-    "array",
-    "null"
-  ]
-}

Changed25 schema fields changedOct 27, 2026
- changedOutput schema / properties / gpu_index / properties / day / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / properties / flags / items / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / properties / flags / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / properties / gpu / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / properties / providers / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / properties / status / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / gpus / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / live / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / provisional / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources / items / properties / ok / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources / items / properties / source / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources_ok / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / sources_total / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / properties / updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / gpu_index / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / manifests / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / manifests / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / methodology / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / token_index / properties / day / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / token_index / properties / updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / token_index / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / verifier / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedOct 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safe read-only profile is covered. The description adds the specific status-content scope, but it does not add operational behavior such as snapshot timing, caching, or refresh semantics beyond saying it reflects 'the status page'.

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?

The description is front-loaded with the main purpose and then enumerates the included status fields efficiently. It is a single dense sentence, which is acceptable but slightly harder to scan than a structured list, and some field enumeration may be redundant with the output schema.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only status tool with a full output schema and strong annotations, the description supplies ample context about what the response covers. No essential information needed to invoke the tool correctly is missing.

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?

This tool has zero parameters, so parameter semantics are not applicable and the baseline is 4. There are no arguments to clarify or disambiguate.

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 clearly identifies the resource: data freshness and source status, including last calculation times, today's index day, source statuses, provider counts, imputed share, and manifest days. It is distinguishable from the price-returning siblings because it reports metadata about freshness and sources rather than prices themselves, though it does not explicitly name those alternatives.

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 implied by 'How fresh the data is' and the enumerated status details, but there is no explicit guidance on when to call this versus the price or verification tools. No exclusions or prerequisites are stated, leaving the agent to infer that this is a read-only status check.

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?