Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidsubmitrequirementstemplates

getProjectsProjectIdSubmitRequirementsTemplates

Retrieves submit requirement templates configured in a project's project.config, including those inherited from its parent projects.

Instructions

Retrieves submit requirement templates configured in project.config and in 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>"
    },
    "name": "getProjectsProjectIdSubmitRequirementsTemplates"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does the load-bearing work: 'Retrieves' signals a read-only operation, 'project.config' identifies the configuration source, and 'and in its parent projects' discloses non-obvious inheritance behavior the agent would otherwise not anticipate. It stops short of stating permission requirements or whether the inherited results are labeled as such.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and resource and ends with the scoping nuance. No filler, no restatement of the title.

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?

An output schema exists, so return values need not be explained, and a one-parameter read tool has modest demands. The definition covers purpose, source, and inheritance scope; only the project-id parameter's expected form is unaddressed.

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 the lone required parameter, but it never mentions project-id directly. The implied project scoping and parent-project inheritance partly convey what the parameter selects, yet the schema carries no format or identifier hints and the description adds none.

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 ('submit requirement templates'), plus the scope: templates configured in project.config and inherited from parent projects. That distinguishes it from the sibling that fetches a single template by ID, though the near-identical sibling naming means the differentiation rests entirely on this sentence.

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 wording implies a read of project-level submit-requirement configuration, and the mention of parent projects hints at inheritance lookups. But it gives no explicit when-to-use guidance, no condition for choosing this bulk listing over the single-template sibling, and no prerequisites or 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