Skip to main content
Glama
Sign In

Zetlyn

by com.zetlyn
OverviewDiscussionsAdmin

Change a watch

update_watch
Idempotent

Change a watch in place: watch another place on the same page (selector), the whole page (whole_page: true), or check it at another interval (every_minutes). The watch keeps its id and history and does not start a new free trial. To watch a different page, make a new watch.

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": {
      "id": "<id>"
    },
    "name": "update_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe watch's id, as list_watches gives it.
selectorNoThe new place's selector, from preview_page or read_place.
whole_pageNoWatch the whole page instead of one place.
notify_whenNoAs in watch_page: {"below": n}, {"above": n}, {"contains": "text"}, {"not_contains": "text"}; null to be told of every change again.
every_minutesNoHow often to check; 15, 5 and 1 need a subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive mutation), the description adds genuinely useful business context: the watch keeps its id and history and does not start a new free trial. That tells the agent the update is cheap and non-destructive in a billing sense, which no annotation conveys. It lacks error/failure behavior on an invalid id.

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?

Three tight sentences, front-loaded with the operation and its options, then the identity/history guarantee, then the boundary condition. No filler and no restatement of the title.

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?

For a 5-parameter mutation with full schema coverage and no output schema, the description covers what matters: scope of change, identity preservation, and when not to use it. Slightly incomplete only in not touching notify_when or error conditions.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description reinforces the meaning of selector, whole_page and every_minutes, but never mentions notify_when or the required id, so it adds little on top of the already thorough schema.

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

Purpose5/5

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

Names a specific verb and resource ('Change a watch in place') and immediately enumerates the three modifiable facets: selector, whole_page, every_minutes. It also distinguishes the operation from its sibling watch_page by stating that a different page requires a new watch rather than an update.

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?

The exclusion is explicit: 'To watch a different page, make a new watch,' which routes the agent away from update_watch toward watch_page. It does not name the sibling tool directly or cover cases like changing notify_when, so it falls just short of full routing guidance.

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

All Zetlyn 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