Skip to main content
Glama
macula-io

Macula MCP

by macula-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

mesh_watch

Watch a mesh topic for inbound facts for a set duration, returning each event with its verified publisher; call again to keep monitoring.

Instructions

Watch a mesh topic for inbound facts for up to duration_seconds, then return whatever arrived, each with its verified publisher. This call BLOCKS for the full duration (or until count events arrive, whichever is first) -- there is no standing subscription to poll later; call this again to keep watching. Realm defaults to io.macula. Presence heartbeats are ordinary facts on "agent.hello"/"agent.goodbye" -- watch those directly to react to an arrival/departure yourself instead of polling mesh_agents. Bytes in event payloads appear as {"$bytes": ""}; pass them back in the same form. dropped: events that reached this server's subscription and were discarded (a subscription's inbox holds 256 events and discards the newest while its reader is behind), since it began; 0 means none were discarded, null means nothing is listening.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoStop early once this many events have arrived.
realmNo32-byte realm id as hex (64 chars) the topic is scoped to. Omit for io.macula.
topicYesTopic name (e.g. 'chat.demo').
duration_secondsNoHow long to watch, in seconds (max 3600).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.37.0
    • removedInput schema / properties / host
      Removed value: -{
-  "description": "Station to connect through, \"host[:port]\". Defaults to station-de-frankfurt.macula.io:4433.",
-  "type": "string"
-}
    • changedInput schema / properties / realm / description
      Previous value: -"32-byte realm as hex (64 chars) the topic is scoped to. Omit for the default all-zero realm. See mesh_call's realm description for the full rationale."New value: +"32-byte realm id as hex (64 chars) the topic is scoped to. Omit for io.macula."
  2. First observedv0.28.7

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: blocking-for-full-duration behavior, early stop at count, no persisted subscription, base64 encoding for byte payloads, and precise meaning of the `dropped` field (inbox capacity 256, newest discarded, 0 vs null). This is unusually rich behavioral disclosure for a tool with zero annotation coverage.

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-loaded with the core action and its blocking trait, and nearly every sentence earns its place. The closing `dropped` sentence is dense and slightly long, but it conveys non-obvious return semantics rather than padding.

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

Completeness5/5

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

No output schema exists, so the description must describe return values itself, and it does: arrived events with verified publishers, plus the `dropped` counter with its 0/null distinction. For a blocking watch tool with no annotations, nothing essential to correct invocation appears missing.

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 per-parameter meaning is already documented. The description still adds value by clarifying the interaction between duration_seconds and count ('blocks for the full duration or until count events arrive, whichever is first') and reaffirming the realm default, going slightly beyond the schema's per-field text.

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 specific verb (watch) on a specific resource (mesh topic) and describes the exact return: inbound facts up to duration_seconds, each with verified publisher. The blocking semantics and lack of standing subscription distinguish it from mesh_read_inbox and mesh_agents 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?

Explicitly says this call BLOCKS and there is no standing subscription to poll later, telling the agent it must call again to keep watching. It also names a concrete alternative path ('watch agent.hello/agent.goodbye directly instead of polling mesh_agents'), which is exactly the when/when-not guidance the dimension asks for.

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

Deploy Server

Other Tools