Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidsubmitrequirementssubmitrequirementi

getProjectsProjectIdSubmitRequirementsSubmitRequirementI

Fetches the definition of a specific submit requirement in a Gerrit project by project ID and requirement ID, so you can inspect its configured rules.

Instructions

Retrieves the definition of a submit requirement that is defined in this 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>",
      "submit-requirement-id": "<submit-requirement-id>"
    },
    "name": "getProjectsProjectIdSubmitRequirementsSubmitRequirementI"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes
submit-requirement-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 implies a read via 'Retrieves' and confirms the lookup is project-scoped, but says nothing about permission/auth requirements, behavior when the ID is unknown, or whether configuration vs. legacy submit requirements are handled differently.

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; the definition is surfaced immediately. The trailing 'that is defined in this project' is mildly redundant with 'submit requirement' but not wasteful enough to hurt.

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?

The existence of an output schema means return values need not be explained, but for a lookup tool with zero annotation coverage and completely undocumented parameters, the description should at least cover identifier formats and failure modes. As written it is too thin for the gaps left by the schema.

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?

With 0% schema description coverage on two required parameters (project-id, submit-requirement-id), the description must compensate, yet it only alludes conceptually to 'this project' and 'submit requirement'. It gives no format guidance such as whether project-id is a numeric ID or URL-encoded path, nor what a submit-requirement-id looks like.

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 ('Retrieves') and resource ('the definition of a submit requirement') scoped to 'this project', which is enough for an agent to tell it apart from the list-style sibling getProjectsProjectIdSubmitRequirements. It stops short of explicitly naming that sibling or the templates siblings 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 Guidelines2/5

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

Use is only implied by the singular 'a submit requirement' versus the plural sibling that presumably lists them. There is no explicit when-to-use, no prerequisites (e.g., needing a known submit-requirement-id), and no exclusions.

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