Skip to main content
Glama
Sign In

Lantern Works GPU Prices: daily GPU rental price comparison

by io.github.connormatthewdouglas
OverviewDiscussionsAdmin

delete_watch

Hosted only. Delete one of your watches by watch_id.

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": {
      "watch_id": "<watch_id>"
    },
    "name": "delete_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
watch_idYes

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already indicate a non-read-only, open-world operation, and the description confirms deletion by watch_id plus a hosted-only restriction. However, it does not disclose side effects, irreversibility, required authorization via api_key, or what happens to associated watch data.

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

Conciseness5/5

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

The description is two short sentences and is front-loaded with the hosted restriction and the delete action. There is no wasted text.

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

Completeness2/5

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

For a destructive mutation tool with two parameters at 0% schema coverage, the definition is too sparse. An output schema exists, so return values need not be described, but the description should still explain authorization, deletion consequences, and the api_key parameter.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that watch_id identifies the watch to delete, but the api_key parameter is not explained at all, leaving a significant gap.

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 uses a specific verb and resource: delete a watch by watch_id. It is clearly distinguishable from sibling read/list tools, but it does not explicitly contrast with related siblings such as list_watches or create_watch_key.

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 constraint given is 'Hosted only'; there is no guidance on when to choose this tool over alternatives or prerequisites beyond the hosted restriction. The intended use is implied by the verb 'delete', but not explicitly developed.

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 toolsInspect
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.

Resources