Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectidtagstagid

getProjectsProjectIdTagsTagId

Retrieves a specific tag for a Gerrit project by project ID and tag ID, returning its details for inspection or reference.

Instructions

Retrieves a tag 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>",
      "tag-id": "<tag-id>"
    },
    "name": "getProjectsProjectIdTagsTagId"
  }
}

Input Schema

NameRequiredDescriptionDefault
tag-idYes
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 provided, so the description carries the full behavioral burden. 'Retrieves' hints at a read operation, but the description says nothing about required access levels, what happens when the tag or project does not exist, whether the tag can be a name instead of an id, or any rate limits. This is a thin disclosure for a tool with zero annotation coverage.

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 front-loaded sentence with no padding or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

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. However, for a tool with two required parameters at 0% schema coverage and no annotations, the definition leaves the agent without parameter or failure-mode context.

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 both required parameters (project-id, tag-id) depend on the description for meaning, yet the description mentions neither. The names are largely self-explanatory, which limits the damage, but no format, id type, or constraint information is added.

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 pairs a specific verb with a specific resource: 'Retrieves a tag of a project.' Together with the name getProjectsProjectIdTagsTagId, an agent can tell it fetches one tag rather than the tag list. It does not explicitly contrast with the sibling getProjectsProjectIdTags, so it falls 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?

The description offers no guidance on when to use this tool versus the list-tags sibling or any other project endpoint. There are no stated prerequisites, no exclusions, and no indication of what selection condition distinguishes this call.

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