Skip to main content
Glama
Sign In

longwatch

by dev.coinop
OverviewDiscussionsAdmin

Look at a source right now

check_now
Destructive

This-session snapshot only — no watch, no cursor. Use when you will not come back. Required by type: url/rss/x402 need url; price needs coin plus above, below, or move_pct_24h; edgar needs ticker or cik. 8-K items are decoded, Form 4 trades parsed, and x402 probes validate the unpaid 402 challenge without sending payment. If the job spans runs, create_watch instead and persist watch_id + key. Costs $0.001 USDC per call via x402 (Base) — no API key, no account. Calling without payment returns 402 with the payment requirements. Free alternative: GET https://longwatch.dev/demo for a free NVDA Form 4 sample, or POST https://longwatch.dev/try for a 24h watch — no wallet needed.

Input Schema

NameRequiredDescriptionDefault
cikNoedgar: SEC CIK, as an alternative to ticker
urlNourl|rss|x402: public URL
bodyNox402: optional JSON object for POST/PUT/PATCH/DELETE, e.g. {"type":"edgar","ticker":"NVDA"}; omit for GET/HEAD
coinNoprice: CoinGecko id, e.g. 'bitcoin'
typeYessource type
aboveNoprice: threshold to compare against
belowNoprice: threshold to compare against
formsNoedgar: form filter, e.g. ["8-K","4"]
methodNox402: 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
tickerNoedgar: stock ticker, e.g. 'NVDA'
move_pct_24hNoprice: 24h move threshold to compare against
expected_schemeNox402: optional expected scheme, e.g. exact
expected_networkNox402: optional expected CAIP-2 network, e.g. eip155:8453
expected_amount_atomicNox402: optional expected token amount in atomic units, e.g. "1000" for 0.001 USDC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
  2. Changed7 schema fields changed
    • 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"New value: +"url|rss|x402: public URL"
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

With annotations already declaring destructive/openWorld/non-idempotent, the description still adds critical context: cost ($0.001 USDC per call on Base), no API key or account, and that an unpaid call returns a 402 with payment requirements rather than failing silently. It also discloses probe behavior (validates the 402 challenge without sending payment) and output decoding (8-K items decoded, Form 4 trades parsed).

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?

Front-loads the most decision-relevant fact (snapshot-only, no cursor) before alternatives, per-type requirements, and pricing — a sensible ordering. It is dense and clause-heavy, and could be broken into shorter sentences, but almost every clause carries distinct information rather than filler.

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 tool with no output schema, the description covers the essentials an agent needs: temporal scope, conditional parameter requirements, payment flow and failure mode, and qualitative description of what comes back per type. What it does not do is hint at the response structure (e.g. snapshot shape or field names), which matters more here because no output schema exists.

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 100%, so the baseline is 3; the description goes beyond the flat schema by stating cross-parameter conditional requirements per type (url/rss/x402 → url; price → coin plus one of above/below/move_pct_24h; edgar → ticker or cik). That conditional routing is not obvious from the schema alone and is genuinely useful, though it doesn't cover the x402 expectation params.

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?

States a concrete verb and a family of concrete resources (url/rss/price/edgar/x402) and immediately names its scope: "this-session snapshot only — no watch, no cursor." It also explicitly contrasts with the watch_* family ("If the job spans runs, create_watch instead"), so an agent can distinguish it from ~18 siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("use when you will not come back"), when-not (multi-run jobs → create_watch with watch_id + key), and two named free alternatives (longwatch.dev/demo and /try) for agents without a wallet. Nothing about selection is left to inference.

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

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