Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidsubmitrequirementstemplatessubmitreq

getProjectsProjectIdSubmitRequirementsTemplatesSubmitReq

Retrieve a project's effective submit requirement template, including inherited definitions from parent projects, to inspect the requirements applied to changes.

Instructions

Retrieves a single effective submit requirement template for a project. The returned template may be defined in the project itself or inherited from one of its 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>",
      "submit-requirement-template-id": "<submit-requirement-template-id>"
    },
    "name": "getProjectsProjectIdSubmitRequirementsTemplatesSubmitReq"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes
submit-requirement-template-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 does add one genuinely useful trait not derivable from the schema: the returned template is 'effective' and may be defined on the project or inherited from a parent project. It does not cover authorization requirements, not-found behavior, or side effects, which is a notable gap for an unannotated tool.

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 core action front-loaded and the inheritance caveat immediately following it. No filler, though the second sentence could be folded into the first without loss.

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 tool is a simple two-parameter read with an output schema, so return values need no explanation and the inheritance caveat covers the main conceptual subtlety. What remains missing is parameter-level meaning and failure-mode behavior, which the absent annotations leave unaddressed.

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% for both required parameters, yet the description says nothing about them explicitly. The 'effective' / 'inherited from parent projects' wording hints that submit-requirement-template-id may resolve to an inherited template rather than a project-local one, which adds some meaning, but project-id formatting and resolution rules are entirely undocumented.

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 single effective submit requirement template for a project.' The word 'single' implicitly separates it from the collection sibling getProjectsProjectIdSubmitRequirementsTemplates, but no sibling is named explicitly, so the differentiation is left partly to inference.

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?

Usage is only implied by the 'single ... template' framing; there is no explicit statement of when to call this versus the list endpoint or the other submit-requirement siblings. Nothing is said about prerequisites, permissions, or what happens when the template ID is unknown or not visible to the caller.

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