Lantern Works GPU Prices: daily GPU rental price comparison

watch_price

Hosted only. Alert your webhook (signed POST) after the daily refresh when a tracked rate for gpu crosses at or below max_hourly_usd, or a change of a watched kind (down/up/new; default down) lands at or below it. Only ELIGIBLE rates match (same contract as compare/estimate): every word of gpu must match the model; 'A100 80GB' or vram_gb=80 never matches a 40GB row; tiers (on-demand, community, marketplace, interruptible/spot, dedicated-monthly, reserved; default all but reserved) never matches another class; a row confirmed sold out never matches (in_stock='require' also skips unknown stock). region: code from availability.available_regions; a rate with no unexpired region evidence stays unresolved and never matches. Each event is delivered at most once per watch (dedupe on event_id). Pass api_key or an Authorization: Bearer header.

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": {
      "gpu": "<gpu>",
      "max_hourly_usd": "<max_hourly_usd>"
    },
    "name": "watch_price"
  }
}

Input Schema

Name	Required	Description	Default
`gpu`	Yes
`kinds`	No
`tiers`	No
`region`	No
`api_key`	No
`vram_gb`	No
`in_stock`	No
`max_hourly_usd`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 30, 2026

addedInput schema / properties / in_stock

Added value: +{
+  "enum": [
+    "exclude_sold_out",
+    "require"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tiers

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / vram_gb
```
Added value: +{
+  "type": "integer"
+}
```

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: signed webhook POST, daily refresh timing, at-most-once delivery per watch, dedupe on event_id, and authentication via api_key or Bearer header. This gives an agent the operational details needed to use the tool safely and correctly.

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 purpose is front-loaded and every clause conveys useful eligibility or delivery information. The single dense paragraph is information-rich but harder to scan than a structured list, which keeps it from a perfect score.

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 complex watch-creation tool with an output schema and sparse annotations, the description covers behavior, eligibility, defaults, delivery semantics, and auth. An agent has enough information to invoke it correctly without needing return-value documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description explains all eight parameters: gpu matching rules, max_hourly_usd threshold, kinds default, tiers classes/default, region code source, vram_gb matching, in_stock behavior, and api_key/header auth. This fully compensates for the bare schema.

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 action: alerting a webhook after the daily refresh when a tracked GPU rate crosses a threshold. It clearly identifies the resource and event, but only indirectly differentiates from watch-management siblings like list_watches or delete_watch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: hosted only, default kind is down, default tiers exclude reserved, and the alert conditions are explicit. It does not explicitly say when to choose this over creating a watch key or searching deals, so it stops short of full alternative guidance.

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

All Lantern Works GPU Prices: daily GPU rental price comparison tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.