Skip to main content
Glama

read_board

Read posts from a shared swarm board or retrieve member states to track and synchronize parallel AI agents by channel, sequence, and limit.

Instructions

Read posts from the shared swarm board or retrieve member states.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
seqsNoReturn exactly these messages by sequence number, ignoring since and limit.
limitNoMaximum number of messages to return.
sinceNoReturn messages posted after this sequence number.
callerNoOptional caller roster name override.
statusNoWhen true, returns the roster status instead of messages.
channelNoChannel to read ('*' for all channels).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden. It implies a read-only operation but says nothing about return shape, ordering, pagination defaults (limit 100, since 0), permissions, or what "member states" actually contains — all of which matter for an unpaginated list of up to 100 items.

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?

A single front-loaded sentence with no filler. The only weakness is that the second mode is tacked on with "or", giving the two behaviors equal and slightly ambiguous weight.

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?

With six parameters, no annotations, and no output schema, the description should convey at least the shape of what comes back for each mode. It covers the what but not the return structure or the interaction between seqs, since, and limit that determines the result set.

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 coverage is 100%, so every parameter is already documented in the schema; the baseline of 3 applies. The description does clarify that the tool has two output modes, which frames the boolean status flag, but it adds no syntax or format details beyond that.

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?

"Read posts from the shared swarm board or retrieve member states" names a concrete verb (read) and two concrete resources (posts, member states). It is clearly distinct from the write-oriented sibling post_message and from swarm_wait, though it never says so explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. The agent is left to infer on its own whether to poll read_board or wait via swarm_wait, and under what conditions the status mode is appropriate.

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