Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectid

getProjectsProjectId

Retrieves detailed information for a specified Gerrit project by project ID, returning a ProjectInfo entity for configuration, access, or review tasks.

Instructions

Retrieves a single project as a ProjectInfo entity.

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": "getProjectsProjectId"
  }
}

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.8/5.0
Behavior2/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 implies a read-only fetch and names the return entity, but says nothing about permissions or visibility requirements, what happens when the project-id does not exist, or whether the response includes restricted fields. For a tool with zero annotation coverage this is thin.

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 nine-word sentence with the verb and resource front-loaded and no filler. It is appropriately sized for a trivial getter, though it is arguably too terse to earn a top score.

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-value structure need not be described. However, for a one-parameter lookup the definition still omits the parameter format and any failure behavior, leaving the agent to guess at the only input it must supply.

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%, so the single parameter "project-id" is documented nowhere. The description does not clarify whether it is a numeric ID, a URL-encoded path, or a namespace/name pair, nor give an example. With only one parameter this gap is small in absolute terms but leaves the only input ambiguous.

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 states a specific verb ("Retrieves") and a clearly bounded resource ("a single project"), which distinguishes it from sibling tools that operate on sub-resources like branches, labels, or commits. It also names the returned entity type (ProjectInfo), so the agent knows what it gets back. It stops short of explicitly naming a sibling alternative, so it is clear but not fully differentiated.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as getProjectsProjectIdChildren or the branch-oriented getters. The agent must infer from the name alone that this is the entry-point call for fetching top-level project metadata.

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