Skip to main content
Glama

Riven SCM: List Merge Requests

riven_scm_list_merge_requests

List merge requests in Riven SCM (scm.rivenai.io). Replaces GitHub pull request listing for Riven projects.

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

Input Schema

NameRequiredDescriptionDefault
stateNoMerge request state ("opened", "merged", "closed", "all").
projectNoProject path or ID (defaults to "rivenai/riven-web").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and does very little with it: it never says whether the call is read-only, whether it paginates or caps results, whether authentication or a specific org membership is required, or what the default state filter is when none is passed. Only the target host is disclosed.

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 zero filler, and the core action and target system are front-loaded before the GitHub-equivalence note. Nothing needs trimming.

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 two-optional-parameter read tool this is minimally viable, but with no annotations and no output schema the description is the only place return shape, pagination, and default-filter behavior could be conveyed, and it conveys none of them. The agent knows what the tool is and where it points, but not what it will get back or how much.

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%, with both 'state' (including a quoted enum of values) and 'project' (with its default path) fully documented in the schema. The description adds no format, syntax, or behavioral meaning beyond that, so the baseline 3 for well-documented schemas 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?

States a specific verb and resource ('List merge requests in Riven SCM') and pins the system to scm.rivenai.io, which distinguishes it from all listed siblings that operate on pipelines, projects, channels, teams, or models. The added note that it replaces GitHub pull request listing further orients the agent, though it does not state the listing scope or default state.

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?

'Replaces GitHub pull request listing for Riven projects' gives a domain-level rule for choosing this over an external GitHub tool, which is genuinely useful. However, it gives no guidance on when to use this versus sibling list tools, no prerequisites, and no advice on selecting a state filter, so the agent must infer the rest.

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.