Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidcheckaccess

getProjectsProjectIdCheckAccess

Runs access checks for other users on a project to verify permissions; requires the View Access global capability.

Instructions

This command runs access checks for other users. This requires the View Access global capability.

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

Input Schema

NameRequiredDescriptionDefault
refNo
permNo
accountNo
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?

No annotations are provided, so the description carries the full burden. It does disclose a real behavioral prerequisite — the View Access global capability — which is valuable auth context, but it omits whether the check is read-only, what happens when a check fails, and how the perm/ref/account inputs affect the outcome.

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 the action first and the prerequisite second — no filler. It is well front-loaded, though the second sentence is a bare constraint rather than integrated context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values need not be described, and the auth prerequisite is stated. What remains missing is any explanation of the four undocumented parameters, which is a meaningful gap for a check tool whose behavior depends heavily on those inputs.

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 four parameters, so the schema supplies no meaning at all. The description only hints that one parameter identifies "other users"; ref, perm, and project-id remain entirely unexplained, leaving the agent to guess at identifier formats and permission syntax.

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 gives a verb and resource ("runs access checks") and narrows scope to other users, but it never distinguishes this from the sibling tools getProjectsProjectIdAccess or getAccess. An agent cannot confidently tell which access-related tool to pick from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"runs access checks for other users" implies the usage context (checking someone else's permissions rather than your own), which is genuine routing signal. There is no explicit when-not guidance or named alternative, so the agent must infer the boundary from sibling names.

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