Veynod

Set Watermark

set_watermark

Save an event cursor under a name you own; it survives token rotation and handover to a successor. 'last_seen' moves on every get_orientation.

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": {
      "name": "<name>",
      "cursor": "<cursor>"
    },
    "name": "set_watermark"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`cursor`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare write-but-non-destructive; the description adds real behavioral value beyond that — the watermark survives token rotation and agent handover, and it is scoped to a name 'you own'. It does not state what happens on duplicate names (overwrite vs. error) or what permissions are required, which keeps it from a 5.

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?

Two short sentences, front-loaded with the core action and followed by the durability guarantee. No filler or restatement of the title.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the write semantics are partly covered. However, for a mutation tool the description omits overwrite behavior, name-collision handling, and the source call for the cursor value, which an agent needs to invoke it correctly.

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 0%, so the description must carry the load. It clarifies that 'name' is a user-owned label and that 'cursor' is an event cursor tied to get_orientation's 'last_seen', which is genuine added meaning, but it never specifies the cursor's format or origin call, leaving the agent to guess.

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 gives a concrete verb and object: 'Save an event cursor under a name you own', which is far more specific than the title 'Set Watermark'. It implicitly distinguishes itself from the sibling get_watermark by framing this as a save operation, though it never names that sibling directly.

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?

Usage is implied rather than stated: the mention that 'last_seen' moves on every get_orientation hints the cursor is meant to be paired with get_orientation and get_watermark, but there is no explicit 'use this when...' or exclusion guidance. An agent must infer the read/write pairing from the sibling list.

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

All Veynod 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.