Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidchildren

getProjectsProjectIdChildren

List direct child projects of a Gerrit project to navigate project hierarchies, with optional recursive listing and limit controls.

Instructions

List the direct child projects of a project.

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": {
      "project-id": "<project-id>"
    },
    "name": "getProjectsProjectIdChildren"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
recursiveNo
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 disclosure burden, and it discloses almost nothing: no permission requirements, no pagination behavior despite a 'limit' parameter, no note on ordering or what happens with deeply nested project trees. Worse, 'direct child' appears to conflict with the presence of a 'recursive' flag, leaving the agent unsure which behavior is the default.

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?

A single front-loaded sentence with no filler, which is the right shape for a simple listing tool. The brevity is close to under-specification rather than elegance, but nothing is wasted or buried.

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?

An output schema exists, so return values need not be explained, but everything else is missing: with no annotations, zero parameter documentation, and an unexplained recursive flag, an agent cannot confidently call this tool beyond the required project-id. The definition is thin relative to a three-parameter traversal operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all three parameters, so the description must compensate and does not. It says nothing about what 'limit' caps, how 'recursive' changes the traversal, or what form 'project-id' takes, leaving every non-required parameter semantically opaque.

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 gives a specific verb ('List') and resource ('direct child projects of a project'), which is enough to distinguish it from the singular sibling getProjectsProjectIdChildrenChildProjectId and from getProjectsProjectId. It stops short of explicitly naming those alternatives, so it is clear but not fully self-differentiating.

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 versus getProjectsProjectIdChildrenChildProjectId or getProjectsProjectId, nor any stated prerequisites such as read access to the parent project. The word 'direct' hints at a non-recursive scope, but the tool's own 'recursive' parameter creates ambiguity that the description never resolves.

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

Deploy Server

Other Tools