Skip to main content
Glama

Riven

Riven Comms: Post Message to Team Channel

riven_comms_post_message

Post a message, rollout summary, or reply thread to a Riven Comms channel (https://rivenai.io/comms). Replaces Slack and Microsoft Teams channel posting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "riven_comms_post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam slug or ID (e.g. "riven", "t-rivenai", "pes-supply"). Defaults to "riven".
channelNoTarget channel name or ID (e.g. "announcements", "town-square", "agents").
messageYesMarkdown message body to post.
root_idNoOptional parent post ID when replying in a thread.
approvedNoSet true when the user has authorized posting this message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 for a mutation tool and largely fails to. It never states whether posting requires the caller to have user authorization (the `approved` flag strongly implies a gate), whether messages are visible org-wide, whether posting notifies members, or whether duplicate posts are deduplicated. The second sentence ('Replaces Slack and Microsoft Teams channel posting') is product positioning, not behavior.

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?

Two sentences, front-loaded with the action and target, so the agent reads the essential fact first. The second sentence about replacing Slack and Teams is soft context rather than required information, keeping it just short of a full 5 for economy.

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

Completeness2/5

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

For a five-parameter write tool with no annotations and no output schema, the description should disclose the authorization gate and what a successful call returns (e.g., a post ID usable as `root_id`). Neither is covered, and no failure or rate-limit conditions are mentioned, so an agent must infer the approval workflow solely from the schema.

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%, so every parameter already has inline documentation including defaults and examples, which sets the baseline at 3. The description adds only slight value by surfacing the 'reply thread' case that motivates `root_id`; it says nothing extra about `team`, `channel`, or the meaning of the `approved` gate.

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 uses a specific verb and resource ('Post a message, rollout summary, or reply thread to a Riven Comms channel') and even names the channel concept, which is enough for an agent to know this is the write path. It does not explicitly contrast with the sibling read/list/search tools, though the verb 'post' is unambiguous against 'list', 'read', and 'search'.

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 guidance, no prerequisites, and no mention of the `approved` authorization step that the schema flags as important for this write tool. The only hint of context is the parenthetical variant 'reply thread', which implies `root_id` usage but is not spelled out.

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.