Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidchildrenchildprojectid

getProjectsProjectIdChildrenChildProjectId

Retrieves a child project by project and child IDs; set recursive to include non-direct descendants.

Instructions

Retrieves a child project. If a non-direct child project should be retrieved the parameter recursive must be set.

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>",
      "child-project-id": "<child-project-id>"
    },
    "name": "getProjectsProjectIdChildrenChildProjectId"
  }
}

Input Schema

NameRequiredDescriptionDefault
recursiveNo
project-idYes
child-project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose one meaningful behavior (non-direct children require `recursive`). It says nothing about permissions, what happens when the project is not actually a child, or error behavior, leaving the read-safety profile implicit.

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?

Two short sentences with no filler, and the conditional rule is stated up front. The phrasing ("If a non-direct child project should be retrieved the parameter recursive must be set") is slightly convoluted and could be tightened.

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?

This is a simple three-parameter read tool with an output schema, so return values need no explanation and the recursive caveat covers the one non-obvious input. Still missing are any permission/auth context and failure modes, which matter for a lookup that can silently differ based on a flag.

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 0%, so the description must compensate. It gives real semantics for `recursive` (required for non-direct children), but `project-id` and `child-project-id` are left entirely to their names, with no format, ID type, or sourcing hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("Retrieves a child project"), but this largely restates the tool name rather than explaining what a child project is or how it differs from the sibling list tool getProjectsProjectIdChildren. An agent can infer singular-vs-list, but the definition does no explicit work to differentiate.

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?

There is a real conditional rule — set `recursive` when the target is not a direct child — which is genuine when-to-use guidance for one parameter. However, there is no guidance on when to call this instead of getProjectsProjectIdChildren or getProjectsProjectId, and no stated prerequisites.

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