Skip to main content
Glama

Riven

Riven Comms: List Channels

riven_comms_list_channels

List channels in a Riven Comms team workspace (e.g. riven, t-rivenai, pes-supply, t-big-sky-dynamics). Use instead of Slack or Microsoft Teams channel listing.

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_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam slug, display name, or ID (defaults to "riven").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "List" implies a read-only, non-destructive operation, but there is no mention of permissions, pagination, result limits, or what happens when a team slug is invalid.

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?

Two short sentences with no filler, and the core action and scope are front-loaded before the alternative-tool note. Nothing is redundant.

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

Completeness4/5

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

For a single optional parameter, read-only listing tool with no output schema, this is nearly sufficient: purpose, examples, and default are all covered. Only secondary details like result size or pagination are absent.

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 a 3, but the description adds concrete example team identifiers (riven, t-rivenai, pes-supply, t-big-sky-dynamics) that clarify the expected slug format beyond the schema text. The default value is already covered by the 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?

States a specific verb and resource ("List channels") scoped to a Riven Comms team workspace, so an agent knows exactly what it returns. It distinguishes itself from Slack/Teams tools but doesn't explicitly separate itself from the sibling riven_comms_list_teams, leaving that boundary to inference.

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?

Gives an explicit alternative: use this instead of Slack or Microsoft Teams channel listing. It supplies the selection condition for the non-Riven choice, but offers no guidance on when to prefer list_channels over other Riven listing/reading tools.

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.