Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccess

getAccess

Lists the access rights of one or more Gerrit projects using repeated project parameters, so you can inspect project permissions and identify permitted actions.

Instructions

Lists the access rights of one or more projects, named by the repeated project parameter.

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

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden. It establishes only that this is a read operation; it says nothing about permissions required, what is returned per project, ordering, pagination, or — critically — what happens when the optional project array is omitted entirely (all projects versus an empty result).

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, correctly leading with the verb and resource. The trailing clause 'named by the repeated project parameter' is slightly awkward but does useful work.

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?

The presence of an output schema relieves the description of explaining return values, and for a one-parameter list tool the scope is fairly small. Still, the optional-parameter semantics and identifier format are left unresolved, which matters for calling it correctly.

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 coverage is 0%, so the description should compensate for the single parameter. It does add value by clarifying that 'project' is a repeated/multi-valued parameter holding project identifiers, but it leaves ambiguous whether those are numeric IDs or names ('named by' reads as a naming verb, not a format spec) and does not describe the zero-length behavior.

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 and resource ('Lists the access rights') scoped to projects, and the 'one or more projects' phrasing signals batch behavior that distinguishes it in spirit from single-project siblings like getProjectsProjectIdAccess. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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?

The phrase 'one or more projects' implies the batch use case and hints that the project parameter is repeated, but there is no explicit statement of when to prefer this over getProjectsProjectIdAccess or getProjectsProjectIdCheckAccess, and no exclusions or preconditions.

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