Skip to main content
Glama

Riven Comms: Search Messages

riven_comms_search_messages

Search posts and threads inside a Riven Comms workspace.

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": {
      "terms": "<terms>"
    },
    "name": "riven_comms_search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam slug or ID (defaults to "riven").
limitNoMaximum matching messages to return (default 12).
termsYesSearch query terms.

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 exist, so the description carries the full disclosure burden, and it discloses almost nothing: read-only nature is only implied, and there is no mention of result ordering, pagination versus the limit parameter, scope of search (workspace-wide vs team-scoped), or permission requirements. The single sentence adds no behavioral context beyond the name.

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?

One short, front-loaded sentence with no filler or redundancy. The brevity is efficient, though the wording "posts and threads" drifts from the tool name's "messages," introducing mild terminological ambiguity.

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-parameter read tool with fully documented schema, the essentials are present. However, with no annotations and no output schema, the definition leaves the agent guessing about scope (workspace-wide versus team-bounded), result shape, and default ordering.

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%, with team default, limit default 12, and terms all documented in the schema, so the baseline is 3. The description adds no extra meaning, such as whether terms supports boolean operators or whether team narrows channel scope.

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 ("Search") and a concrete resource domain ("posts and threads inside a Riven Comms workspace"), which separates it from siblings like riven_comms_post_message or riven_comms_read_channel. It never mentions siblings or the more precise noun "messages" used in the tool name, so the distinction is inferable rather than explicit.

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 guidance at all: nothing says whether to prefer this over riven_comms_read_channel for browsing, or whether it searches across channels/teams or only within one. The only hint is the word "Search" itself, which is implied usage rather than stated guidance.

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.