Skip to main content
Glama

Watch for updates

evuun_watch
Read-onlyIdempotent

Read the arrangement event stream after a sequence number, for hosts that cannot receive pushes.

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": {
      "arrangement_id": "<arrangement_id>"
    },
    "name": "evuun_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
arrangement_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that this is a pull/poll substitute for push delivery, but it leaves out whether it returns immediately or long-polls, what an empty result means, and whether stream ordering or durability is guaranteed. For a polling/cursor tool those omissions matter, so the added value beyond annotations is modest.

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?

It is a single sentence with zero redundant wording, and the core behavior plus its routing condition are front-loaded.

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?

With no output schema, 0% schema coverage on three parameters, and no annotations describing timing, the one-line description leaves too much unexplained: 'limit' is never mentioned, the shape of returned events is not hinted at, and there is no instruction on how to page or resume. It is not sufficient for an agent to call this tool correctly without experimenting.

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 carries the full burden. It clarifies that 'after' is a sequence-number cursor, which is genuinely useful, but says nothing about 'limit' or about the arrangement_id format or scope. Only one of the three parameters gains meaning over the raw schema.

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 pairs a specific verb with a concrete resource: 'Read the arrangement event stream after a sequence number.' It also names the condition that characterizes this tool (hosts that cannot receive pushes), which distinguishes it from a push-based path. It stops short of naming a sibling tool as the alternative, so it is clear but not fully differentiated.

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?

'For hosts that cannot receive pushes' is a real when-to-use condition that an agent can evaluate, and it implicitly marks push-capable hosts as the case where this tool is not needed. There is no guidance on polling cadence, when to stop watching, or how to resume from a prior cursor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources