Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidstatisticsgit

getProjectsProjectIdStatisticsGit

Fetch Git repository statistics for a specified project to assess repository size and activity.

Instructions

Return statistics for the repository of a project.

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

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.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about permissions, whether stats are cached/live, the time range covered, or the granularity of the returned metrics. 'Return' implies a read-only operation, but that is the only behavioral signal present.

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

Conciseness3/5

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

One short front-loaded sentence with no filler, which is structurally sound. It is concise to the point of under-specification, though — the brevity comes at the cost of the information an agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 described, but the definition still fails to say what category of statistics is returned or how it relates to sibling project endpoints. For a stats endpoint in a large API surface, the description is too thin to route correctly.

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 the single required project-id parameter, and the description only obliquely implies it via 'of a project'. It does not state the expected identifier format (numeric ID vs. path-encoded namespace/project) or whether a URL-encoded full path is accepted, which is the kind of detail the schema lacks.

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 supplies a specific verb ('Return statistics') and a resource scope ('the repository of a project'), so the agent knows this is a read of repo-level stats. However, 'statistics' is undefined — commit counts, size, contributor data, branch counts? — and nothing distinguishes it from the many other getProjectsProjectId* siblings that also read project data.

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 guidance on when to use this tool, no prerequisites, and no mention of any alternative for related data. The agent is left to infer its purpose entirely from the name and the vague word 'statistics'.

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