Skip to main content
Glama

Riven

Riven Comms: List Team Workspaces

riven_comms_list_teams

List sovereign Riven Comms (0.0.1) team workspaces across the tenant estate (replaces Slack workspaces and Microsoft Teams orgs).

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

Input Schema

NameRequiredDescriptionDefault
include_personalNoInclude personal workspaces (default false).

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 provided, so the description carries the full behavioral burden. It discloses tenant-wide scope and the Slack/Teams replacement mapping, but omits read-only confirmation, permission requirements, pagination, ordering, and return behavior.

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?

The definition is a single front-loaded sentence with no wasted wording. The parenthetical mapping adds useful context without becoming verbose.

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 simple one-optional-parameter list operation with full schema coverage and no output schema, the description provides enough scope and domain mapping to call the tool. Missing usage and behavioral details keep it from being fully complete.

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 description coverage is 100%, and the sole parameter include_personal is fully documented by the schema including its default. The description adds no additional parameter meaning, so the baseline score of 3 applies.

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?

The description gives a specific verb ('List') and resource ('team workspaces'), plus scope ('across the tenant estate') and a mapping to Slack workspaces/Microsoft Teams orgs. It does not explicitly contrast with siblings such as riven_comms_list_channels, so it is clear but not fully sibling-differentiating.

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 use case is implied by 'List team workspaces,' but the description adds no routing guidance for choosing this tool over sibling list/search 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.