Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidtags

getProjectsProjectIdTags

Retrieve and list all tags for a specified Gerrit project, with optional filtering by name or regex, sorting, and pagination controls.

Instructions

List the tags 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": "getProjectsProjectIdTags"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
matchNo
regexNo
startNo
sort-byNo
descendingNo
project-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

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 supplied, so the description bears the full disclosure burden. "List" implies a read-only operation, but nothing is said about pagination, default result size, filtering behavior, or error conditions. The description leaves an agent with little beyond the bare intent.

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?

The single sentence is clean and front-loaded with no wasted words. However, its brevity reflects under-specification rather than efficient communication of the tool's contract.

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 explained. But for a 7-parameter listing tool with no annotations and zero parameter coverage, one sentence is far too thin; the filtering and pagination arguments are the main risk of misuse and are entirely unaddressed.

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

Parameters1/5

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

Schema description coverage is 0% across 7 parameters, and the description mentions none of them. Filters (match, regex), paging (limit, start), and ordering (sort-by, descending) are completely undocumented anywhere, so the agent cannot know their semantics or interactions.

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 and resource: "List the tags of a project." That distinguishes it from the singular sibling getProjectsProjectIdTagsTagId, which presumably fetches one tag. It does not name that sibling explicitly, so it stops short of a 5.

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 rather than getProjectsProjectIdTagsTagId, nor any mention of prerequisites such as permissions or project access. The agent must infer usage purely from the one-line purpose.

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