Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidaccess

getProjectsProjectIdAccess

Lists the access rights for a single Gerrit project, so you can audit read, write, and administration permissions.

Instructions

Lists the access rights for a single 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": "getProjectsProjectIdAccess"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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; 'Lists' implies a read but nothing is said about required permissions or visibility scope of who may list access rights. It also does not mention pagination or result size, leaving behavior mostly undisclosed.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is arguably too terse for a tool with zero annotation coverage, but nothing in it is wasted.

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?

An output schema exists, so return-value detail need not be repeated, and the one parameter is named. However, for a permissions-sensitive listing tool with no annotations and multiple similar siblings, the definition omits the differentiation and access context an agent would need to select it confidently.

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% for the single project-id parameter, but the phrase 'a single project' does clarify that the id identifies one project rather than accepting filters or a list. That is modest added meaning and nothing more, such as the id format or whether it accepts a path vs numeric id.

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?

States a specific verb ('Lists') and resource ('access rights') scoped to 'a single project', so an agent knows exactly what it returns. It does not distinguish itself from close siblings such as getProjectsProjectIdCheckAccess or getAccess, which keeps it from a 5.

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?

No when-to-use or when-not-to-use guidance is given. With siblings like getProjectsProjectIdCheckAccess (likely a permission check) and getAccess (likely broader scope), the definition leaves the choice entirely to inference.

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