Skip to main content
Glama

Inspect what can be reviewed

list_review_scope

Lists branches or commits so you can select a review scope for start_review, with optional repository path, range, and entry limit.

Instructions

Lists branches or commits so you can choose a scope for start_review.

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": {
      "kind": "<kind>"
    },
    "name": "list_review_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat to list.
limitNoMax entries. Default 50.
rangeNoGit range for commits, e.g. origin/dev..HEAD.
repoPathNoRepository path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only listing but never states that explicitly, and it says nothing about result ordering, truncation via the limit parameter, or whether listing has side effects or network cost. Only the workflow linkage to start_review adds 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource and the downstream purpose front-loaded, and no redundant or filler wording.

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 read-only list tool with fully documented parameters and no output schema, the description covers what it does and why an agent would call it. The main remaining gap is return-shape and truncation behavior, which matters somewhat less given the schema-defined limit.

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 every parameter (kind, limit, range, repoPath) is documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 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 uses a specific verb plus resource ('Lists branches or commits') and ties the output to a concrete purpose: choosing a scope for start_review. It is clearly distinguishable from siblings like get_review or resolve_comments, though it does not explicitly contrast with list_pull_requests, which is the nearest listing alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for use — call this before start_review to pick a scope — which is precisely the workflow decision an agent needs. It stops short of explicit exclusions or prerequisites (e.g., that a repoPath must point at a valid checkout), so it is not a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.