Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidsubmitrequirements

getProjectsProjectIdSubmitRequirements

Retrieves all submit requirements for a project; set inherited to include requirements from parent projects. Use it to inspect Gerrit project submission rules.

Instructions

Retrieves a list of all submit requirements for this project. The inherited parameter can be supplied to also list submit requirements from parent projects.

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

Input Schema

NameRequiredDescriptionDefault
inheritedNo
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it leaves important traits undisclosed: whether this is a paged result, what order requirements are returned in, and what the default of 'inherited' is. The only behavioral insight is that inheritance pulls in requirements from parent projects, and even that concerns a parameter rather than execution behavior.

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 tight sentences with the resource statement front-loaded and the parameter note second. Nothing is wasted, though the second sentence could also cover the default value at no extra length cost.

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?

This is a simple read-only list endpoint with only two parameters and an output schema, so return-value documentation is unnecessary. The description covers the resource and the one non-obvious parameter, leaving only minor gaps like pagination and the inherited default.

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 for both parameters. It usefully explains that 'inherited' expands the result set to parent projects, but does not state the default (presumably false) or clarify that 'project-id' identifies the project whose requirements are fetched.

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: "Retrieves a list of all submit requirements for this project." That clearly differentiates it from the template and single-requirement siblings, though it does not explicitly name them as alternatives.

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 description's guidance is limited to the optional 'inherited' parameter and its effect, which implies when to set it. It offers no explicit when-to-use versus when-not, and no direction about choosing between this list endpoint and the sibling single-requirement or template endpoints.

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