Skip to main content
Glama
Sign In

Compute Screener

by com.computescreener
OverviewDiscussionsAdmin

Check a published price

verify_price
Read-onlyIdempotent

How a published daily value can be checked: whether it is final, and for a final day its manifest (every file it was computed from with its SHA-256, the factors in force, the calculation code's SHA-256 and the final values) and the command that recomputes it from the public files with the published code. Omit date for the latest day with a manifest.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe index day, YYYY-MM-DD (US Central for GPUs, UTC for companies).
nameYesA GPU or an AI company.

Output Schema

NameRequiredDescriptionDefault
dateYes
kindYes
nameYes
unitNo
statusYesverifiable: final, with a manifest; provisional: the day is not over; pending: final, its manifest comes with the next update; rebuilt_history: before manifests began; restated: final, as recomputed by a later method version (Token Price Index 2.0 recomputed every token day to 2026-10-27), with version 1's manifest for that day when it has one; no_value: nothing published that day
manifestNo
publishedNoThe value as published for that day
recomputeNo
explanationYes
methodologyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous 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"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "RTX PRO 6000",
+  "L40S",
+  "RTX A6000",
+  "RTX 6000 Ada",
+  "L40",
+  "RTX 5090",
+  "RTX 4090",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi",
+  "StepFun",
+  "MiniMax",
+  "Mistral",
+  "Reflection AI",
+  "NVIDIA",
+  "Thinking Machines"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "H100",
-  "H200",
-  "A100",
-  "B200",
-  "B300",
-  "RTX PRO 6000",
-  "L40S",
-  "RTX A6000",
-  "RTX 6000 Ada",
-  "L40",
-  "RTX 5090",
-  "RTX 4090",
-  "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"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous 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"
-]New value: +[
+  "H100",
+  "H200",
+  "A100",
+  "B200",
+  "B300",
+  "RTX PRO 6000",
+  "L40S",
+  "RTX A6000",
+  "RTX 6000 Ada",
+  "L40",
+  "RTX 5090",
+  "RTX 4090",
+  "Anthropic",
+  "OpenAI",
+  "Google",
+  "xAI",
+  "Meta",
+  "Moonshot AI",
+  "Alibaba",
+  "DeepSeek",
+  "Z.ai",
+  "Xiaomi",
+  "StepFun",
+  "MiniMax",
+  "Mistral",
+  "Reflection AI",
+  "NVIDIA",
+  "Thinking Machines"
+]
  4. Changed1 schema field changed
    • 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"
+]
  5. Changed1 schema field changed
    • 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"
+]
  6. Changed3 schema fields changed
    • 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"
+]
    • changedOutput schema / properties / status / description
      Previous value: -"verifiable: final, with a manifest; provisional: the day is not over; pending: final, its manifest comes with the next update; rebuilt_history: before manifests began; no_value: nothing published that day"New value: +"verifiable: final, with a manifest; provisional: the day is not over; pending: final, its manifest comes with the next update; rebuilt_history: before manifests began; restated: final, as recomputed by a later method version (Token Price Index 2.0 recomputed every token day to 2026-10-27), with version 1's manifest for that day when it has one; no_value: nothing published that day"
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "verifiable",
-  "provisional",
-  "pending",
-  "rebuilt_history",
-  "no_value",
-  null
-]New value: +[
+  "verifiable",
+  "provisional",
+  "pending",
+  "rebuilt_history",
+  "restated",
+  "no_value",
+  null
+]
  7. Changed1 schema field changed
    • 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"
+]
  8. Changed30 schema fields changed
    • changedOutput schema / properties / date / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / explanation / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • 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 / manifest / properties / code_files / additionalProperties / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / code_files / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / created / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / factors / properties / calibrated_on / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / factors / properties / sha256 / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / factors / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / items / properties / path / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / items / properties / role / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / items / properties / sha256 / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / items / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / files / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / matches_published / type
      Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / methodology_version / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / manifest / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / methodology / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / recompute / properties / command / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / recompute / properties / daily_results / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / recompute / properties / verifier / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / recompute / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "verifiable",
-  "provisional",
-  "pending",
-  "rebuilt_history",
-  "no_value"
-]New value: +[
+  "verifiable",
+  "provisional",
+  "pending",
+  "rebuilt_history",
+  "no_value",
+  null
+]
    • changedOutput schema / properties / status / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / unit / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  9. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context by disclosing that results are split into final vs non-final days and that final days carry a manifest plus a reproducible recompute command. It does not address what makes a day non-final or how heavy the manifest payload is.

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 dense sentence with a deeply nested parenthetical listing manifest contents, which makes it harder to parse than necessary. The useful omission rule is present but buried at the end rather than 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 values need not be spelled out, and the description covers finality, manifest composition, and date omission. Gaps remain around what 'final' versus provisional means and how this tool relates to the price-reading siblings, which matters for a verification tool sitting in a large family.

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?

Schema coverage is 100%, so both parameters are self-documented, giving a baseline of 3. The description goes beyond the schema by explaining the consequence of omitting date (returns the latest day that has a manifest), a behavioral detail the schema does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says what the response contains (finality flag, manifest with file SHA-256s, factors, code SHA-256, final values, recompute command), so the resource is identifiable. But it is framed indirectly as 'How a published daily value can be checked' rather than a verb+resource statement, and it never distinguishes this verification tool from siblings like get_gpu_price_at or get_price_history.

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?

The only usage instruction is 'Omit date for the latest day with a manifest,' which clarifies parameter omission but not tool selection. There is no statement of when to use verify_price versus simply reading a price via get_gpu_prices or get_gpu_price_at, which is the main decision an agent faces among these 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 toolsInspect
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