Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigserversubmitrequirements

getConfigServerSubmitRequirements

Lists globally defined submit requirements added programmatically through the SubmitRequirement extension point, helping you review configured Gerrit submission rules.

Instructions

Lists the globally defined submit requirements (submit requirements that are added programmatically via the SubmitRequirement extension point).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getConfigServerSubmitRequirements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and "Lists" does signal a read-only, non-mutating operation. The parenthetical adds genuine domain context (programmatic vs. configured requirements) beyond the name, but nothing is said about permissions, ordering, or whether project-level requirements are excluded from the result.

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?

One front-loaded sentence with the key scope word ("globally") placed early. The parenthetical repeats the phrase "submit requirements" verbatim, which is slightly redundant, but the total length is appropriate.

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?

An output schema exists, so return values need not be explained, and with no parameters there is little else to cover. Still, for a global-config read with zero annotations, an agent would benefit from knowing the permission level required and whether the result excludes project-scoped requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description does not mislead about inputs.

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 ("Lists") and a scoped resource ("globally defined submit requirements"), and the parenthetical clarifies that these are programmatically added via the SubmitRequirement extension point. The word "globally" implicitly contrasts with the project-scoped submit-requirement siblings, but no sibling is named explicitly.

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: an agent can infer this is the tool for global (non-project) submit requirements rather than getProjectsProjectIdSubmitRequirements, but the description never states when to prefer it or what the alternative covers. No prerequisites or exclusions are given.

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