Skip to main content
Glama

Lantern Works GPU Prices: daily GPU rental price comparison

create_watch_key

Hosted only, free, opt-in. Register a webhook for GPU price alerts and get an api_key plus a webhook signing secret (both shown ONCE; store them). webhook_url must be public https. email is optional contact only (no mail is sent). No payment. Stored: a hash of the key, the webhook URL, optional email, your watches and per-key counts.

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": {
      "webhook_url": "<webhook_url>"
    },
    "name": "create_watch_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
webhook_urlYes

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Discloses the important non-obvious traits: secrets are shown ONCE and must be stored, no payment is required, no mail is sent, and exactly what is persisted (key hash, webhook URL, optional email, watches, per-key counts). This goes well beyond the readOnlyHint=false and openWorldHint=true annotations.

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?

Dense, front-loaded fragments with no filler; the one-time-secret warning appears early where it matters most. The telegraphic phrasing ('Hosted only, free, opt-in') is slightly clipped but still readable.

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, yet the description still usefully flags the one-time visibility of the returned credentials and the storage footprint. Given only two parameters and full schema/annotation coverage, what remains missing is only the relationship to sibling watch-creation tools.

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 0%, so the description must compensate, and it does: webhook_url must be a public https URL, and email is optional and used only as contact info. Both parameters are given meaning the bare schema lacks, though exact URL validation rules are not spelled out.

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 verb and resource: 'Register a webhook for GPU price alerts and get an api_key plus a webhook signing secret.' The credential-issuing framing distinguishes it from sibling watch_price, though it never names that sibling explicitly.

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?

'Hosted only, free, opt-in' gives an availability condition but no guidance on when to call this versus watch_price or list_watches. The agent must infer that this is the setup step before watches can be created.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.