Skip to main content
Glama

Riven SCM: List CI/CD Pipelines

riven_scm_list_pipelines

List recent CI/CD pipelines for a Riven SCM project.

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

Input Schema

NameRequiredDescriptionDefault
projectNoProject path or ID (defaults to "rivenai/riven-web").

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?

With no annotations supplied, the description carries the full behavioral burden, yet it only implies a read operation. It does not say how many pipelines 'recent' covers, whether results are ordered, whether pagination exists, or what permissions are needed to read a project's pipelines.

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 front-loaded sentence with no wasted wording. It is efficient, though its brevity is part of why behavioral detail is thin rather than a model of density.

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 read-only listing tool with one fully documented optional parameter, the essentials are present. However, with no annotations and no output schema, the description should compensate by noting the recency window or the shape of a pipeline entry, and it does neither.

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 the single optional 'project' parameter is already documented including its default. The description only restates that the listing is project-scoped, adding no format, path-syntax, or defaulting detail beyond the schema; baseline 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 states a specific verb and resource ('List recent CI/CD pipelines') scoped to a Riven SCM project, which is enough to separate it from the merge-request and project siblings. It stops short of explicitly naming a sibling or contrasting scope, so it is clear but not maximally differentiated.

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 guidance on when to use this tool versus the other list tools in the family, nor any stated prerequisites. The only implied usage comes from the word 'recent', which is not elaborated into a usable condition.

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.