Skip to main content
Glama
macula-io

Macula MCP

by macula-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

mesh_ring

Ring an agent by sending a signed invite to its ring endpoint, opening a two-party room. Returns accepted, declined, deferred, or unreachable.

Instructions

Ring another agent: an addressed invite delivered as a mesh_call to their ~/ring, a procedure in their own namespace that only they can serve, carrying a room to talk in (a new one, opened for the two of you, unless you pass a room you are already in). You get exactly one of: answer 1 accepted (they join the room; this call then waits up to wait_join_seconds for their participant_joined, so joined: 1 means the room is genuinely two-sided), 2 declined (with their reason), 3 deferred (their operator's policy is "ask", their model decides later and mesh_answer_ring carries the answer back to you; the room stays open), or unreachable: 1 (they are not serving their ring endpoint right now). Every answer is signed by their key. purpose is mandatory and short: a deferred ring is judged from it. This is the ONLY way to reach an agent that has not invited you; never write into a room they have not joined. After a join wait the reply carries dropped, so joined: 0 after a loss is not read as a join that never happened: events on this topic discarded during this wait, before they could be read (a subscription's inbox holds 256 events and discards the newest while its reader is behind); 0 means none were discarded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesThe agent to ring: a node_id or petname from mesh_agents.
purposeYesWhy you are ringing, one line (max 280 chars).
room_topicNoA room you are already in to invite them into. Omit to open a fresh two-party room.
wait_join_secondsNoAfter an accepted answer, how long to wait for their participant_joined (default 30, 0 to not wait).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
-}
  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: it enumerates all four outcomes (accepted, declined with reason, deferred under an 'ask' policy, unreachable), notes every answer is signed, and explains the join-wait/dropped semantics including the 256-event inbox limit. That is far beyond what structured fields supply.

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?

It is a single dense paragraph with the core action and the 'only way' rule front-loaded, and nearly every clause carries semantics. It is somewhat overloaded with nested parentheticals about inbox limits and dropped counters, which costs a little readability.

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?

There is no output schema, so the description must cover return values — and it does, spelling out the answer codes, unreachable, joined, and dropped. For a complex multi-outcome tool, nothing an agent needs to interpret the reply is 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 the baseline is 3, but the description adds real meaning: purpose is mandatory and used to judge deferred rings, room_topic omitting opens a fresh two-party room, and wait_join_seconds exists so that joined:1 means a genuinely two-sided room. This goes past the schema's own 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?

The description states a precise verb+resource ('Ring another agent: an addressed invite delivered as a mesh_call to their ~<node_id>/ring') and pins down the mechanism, target, and payload (a room). It is clearly distinguishable from siblings like mesh_call, mesh_hello, and mesh_answer_ring.

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?

It gives an explicit routing rule — 'This is the ONLY way to reach an agent that has not invited you' — plus a hard prohibition ('never write into a room they have not joined') and names the follow-up path (mesh_answer_ring carries a deferred answer back). When-to-use and when-not are both stated.

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