longwatch

Create a free trial watch

try_watch

Destructive

Create a free trial watch — no payment, no wallet, no account. Same watch types as create_watch (url, rss, price, edgar, x402). The trial runs for 24h, one at a time per caller, and cannot use webhooks. Use this first to see what the alerts look like before paying. Free — no payment required.

Input Schema

Name	Required	Description
`cik`	No	edgar: SEC CIK, as an alternative to ticker
`url`	No	url\|rss\|x402: public URL to watch
`body`	No	x402: optional JSON object for POST/PUT/PATCH/DELETE, e.g. {"type":"edgar","ticker":"NVDA"}; omit for GET/HEAD
`coin`	No	price: CoinGecko id, e.g. 'bitcoin'
`type`	Yes	watch type
`above`	No	price: alert when USD price crosses above this
`below`	No	price: alert when USD price crosses below this
`forms`	No	edgar: form filter, e.g. ["8-K","4"]
`method`	No	x402: HTTP method, default GET. POST/PUT/PATCH/DELETE can modify the target even without payment; use only on a target you are authorized to probe
`ticker`	No	edgar: stock ticker, e.g. 'NVDA'
`move_pct_24h`	No	price: alert when \|24h change\| exceeds this percent
`expected_scheme`	No	x402: optional expected scheme, e.g. exact
`expected_network`	No	x402: optional expected CAIP-2 network, e.g. eip155:8453
`expected_amount_atomic`	No	x402: optional expected token amount in atomic units, e.g. "1000" for 0.001 USDC

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 30, 2026

addedInput schema / properties / body / description

Added value: +"x402: optional JSON object for POST/PUT/PATCH/DELETE, e.g. {\"type\":\"edgar\",\"ticker\":\"NVDA\"}; omit for GET/HEAD"

addedInput schema / properties / expected_amount_atomic / description

Added value: +"x402: optional expected token amount in atomic units, e.g. \"1000\" for 0.001 USDC"

addedInput schema / properties / expected_network / description

Added value: +"x402: optional expected CAIP-2 network, e.g. eip155:8453"

addedInput schema / properties / expected_scheme / description
```
Added value: +"x402: optional expected scheme, e.g. exact"
```

addedInput schema / properties / method / description

Added value: +"x402: HTTP method, default GET. POST/PUT/PATCH/DELETE can modify the target even without payment; use only on a target you are authorized to probe"

Changed7 schema fields changedAug 26, 2026

addedInput schema / properties / body

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

addedInput schema / properties / expected_amount_atomic

Added value: +{
+  "type": [
+    "string",
+    "number"
+  ]
+}

addedInput schema / properties / expected_network
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / expected_scheme
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / method

Added value: +{
+  "enum": [
+    "GET",
+    "POST",
+    "PUT",
+    "PATCH",
+    "DELETE",
+    "HEAD"
+  ],
+  "type": "string"
+}

changedInput schema / properties / type / enum

Previous value: -[
-  "url",
-  "rss",
-  "price",
-  "edgar"
-]New value: +[
+  "url",
+  "rss",
+  "price",
+  "edgar",
+  "x402"
+]

changedInput schema / properties / url / description

Previous value: -"url|rss: page or feed URL to watch"New value: +"url|rss|x402: public URL to watch"

AddedAug 17, 2026
RemovedAug 5, 2026
AddedAug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations declare destructiveHint=true and openWorldHint=true, so the safety bar is lower, yet the description adds real operational context: 24h lifetime, one concurrent trial per caller, no webhook delivery, and no wallet/payment. It does not explain why the tool is flagged destructive (the schema hints at x402 write methods, not the description), so the disclosure is strong but incomplete.

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 core constraint and the types are front-loaded in the first two sentences, and the trial limits follow logically. The closing "Free — no payment required" restates the opening "no payment, no wallet, no account," making the final sentence partly redundant.

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 14-parameter creation tool with no output schema, the description supplies the key behavioral envelope (trial duration, concurrency, webhook limitation, cost) that an agent needs before calling. It leans on the fully documented schema for parameter details, which is appropriate, though the destructive x402-method risk is only surfaced in the schema.

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% with 14 well-documented parameters, so the schema already carries parameter meaning. The description only repeats the type enum values that the schema lists, adding no syntax, defaults, or per-type requirements beyond that.

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?

The description states a specific verb and resource ("Create a free trial watch") and explicitly enumerates the five watch types it supports, tying it to the create_watch sibling rather than leaving the relationship implicit. An agent can distinguish this from create_watch and from the individual watch_* helpers on the first read.

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?

It gives a clear directive: "Use this first to see what the alerts look like before paying," which tells the agent when to prefer it over the paid path. It also states the trial constraints (24h, one at a time per caller, no webhooks), but it never explicitly says when to switch to create_watch, leaving that inference to the reader.

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

All longwatch tools Inspect

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

Need Help?