Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidconfig

getProjectsProjectIdConfig

Retrieve a Gerrit project's effective configuration, including values inherited from parent projects, to verify project settings and permissions.

Instructions

Gets some configuration information about a project. Note that this config info is not simply the contents of project.config; it generally contains fields that may have been inherited 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": "getProjectsProjectIdConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
project-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add one genuinely useful behavioral fact: the returned config is not merely project.config and may include values inherited from parent projects. Beyond that it says nothing about permissions, side effects, or how inheritance is resolved, leaving most behavioral disclosure to the output schema.

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 sentences, front-loaded with the purpose and followed by the one non-obvious caveat about inheritance. No filler, though the first sentence's vagueness ('some configuration information') costs a little precision.

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 the inheritance caveat covers the main surprise an agent would hit. However, for a tool embedded in a large family of similar config endpoints, the definition does nothing to help selection or parameter use.

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?

There is one required parameter (project-id) with 0% schema description coverage, so the description should clarify it but never mentions the parameter. The name 'project-id' is largely self-explanatory and the tool is single-purpose, which softens the gap but does not eliminate it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it 'Gets some configuration information about a project,' which identifies the verb and resource but stays deliberately vague about which configuration. It does not distinguish this tool from sibling config endpoints such as code_owners_getProjectsProjectIdCodeOwnersProjectConfig, so an agent must infer the difference from the name alone.

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?

There is no statement of when this tool should be used instead of the many sibling getProjectsProjectId* endpoints, nor any prerequisites or exclusions. The only guidance is a note about what the result contains, not when to call it.

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