Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojects

getProjects

Lists Gerrit projects accessible to the caller, with optional filtering by prefix, regex, or substring.

Instructions

Lists the projects accessible by the caller, optionally filtered by prefix, regex, or substring.

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": "getProjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
rNo
allNo
treeNo
typeNo
limitNo
matchNo
queryNo
startNo
stateNo
formatNo
prefixNo
descriptionNo
has-acl-forNo
show-branchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: no pagination behavior despite limit/start parameters, no ordering, no default scope, no statement of what 'accessible' means in terms of permissions or visibility. The only real behavioral hint is that results are caller-scoped, which is genuine but thin for a 14-parameter listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded, free of filler, and grammatically clean. However, brevity here shades into under-specification: the same sentence length could have carried pagination or scope details without becoming bloated.

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?

With 14 unannotated, undocumented parameters, no output schema, and no annotations to fall back on, the definition is far too sparse for the tool's complexity. An agent cannot tell what most parameters do, what the response shape is, or whether results are paginated, so calling it correctly would require guesswork.

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 14 parameters, so the description must compensate and it does not. It maps loosely to three concepts ('prefix', bare 'r' presumably regex, and a substring-style query), leaving 'all', 'tree', 'type', 'state', 'format', 'description', 'has-acl-for', 'show-branch', 'limit', and 'start' entirely undefined anywhere in the definition.

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 pairs a specific verb ('Lists') with a specific resource ('projects') and adds the scope 'accessible by the caller', so the agent knows exactly what this tool returns. It stops short of distinguishing itself from siblings such as getProjectsProjectId or getAccountsAccountIdWatchedProjects, so it cannot be told apart from those purely on the description alone.

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?

It states that filtering is optional ('optionally filtered by prefix, regex, or substring') but gives no guidance on when to use this tool versus the many project-scoped siblings. There are no exclusions, no prerequisites, and no indication of which entry point an agent should prefer for a single project lookup.

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