Skip to main content
Glama

Riven

Riven Comms: Read Channel Messages

riven_comms_read_channel

Read recent messages from a Riven Comms channel (e.g. town-square, announcements, agents, alerts).

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": "riven_comms_read_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam slug or ID (defaults to "riven").
limitNoMaximum messages to return (1-50, default 15).
channelNoChannel name or ID (e.g. "town-square", "announcements", "agents").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. The verb "Read" implicitly signals a non-destructive operation and "recent" bounds the scope, but nothing is said about ordering, truncation or pagination behavior, permission requirements, or what a result entry contains.

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 wasted clauses. The parenthetical channel examples slightly duplicate the schema's own examples, but the cost is minimal.

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?

For a simple three-optional-parameter read tool, the definition is adequate: all inputs are documented and the action is unambiguous. With no output schema to lean on, however, the description omits the shape and ordering of returned messages, which an agent would need to plan a follow-up.

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 team, limit, and channel are all documented with defaults and ranges in the schema itself. The description only repeats the channel examples already present in the schema and adds no extra meaning such as whether channel accepts an ID versus a name differently.

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?

States a specific verb and resource ("Read recent messages from a Riven Comms channel") and gives concrete channel examples, so the agent knows precisely what it fetches. It stops short of distinguishing itself from the sibling riven_comms_search_messages, leaving the browse-vs-search boundary to be inferred.

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?

"Recent messages" implies a latest-messages browse scenario, which faintly contrasts with search, but there is no explicit when-to-use/when-not guidance and no mention of the search sibling. The agent must infer that this tool cannot filter by text or author.

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.