Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getprojectsprojectiddashboardsdashboardid

getProjectsProjectIdDashboardsDashboardId

Retrieves a Gerrit project dashboard using project and dashboard IDs, including inherited dashboards from a parent project when specified.

Instructions

Retrieves a project dashboard. The dashboard can be defined on that project or be inherited from a parent 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>",
      "dashboard-id": "<dashboard-id>"
    },
    "name": "getProjectsProjectIdDashboardsDashboardId"
  }
}

Input Schema

NameRequiredDescriptionDefault
inheritedNo
project-idYes
dashboard-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 disclose one genuinely useful behavioral trait: the dashboard may be inherited from a parent project, which affects what the agent receives. It does not cover permissions, behavior when the IDs are unknown, or how inheritance interacts with the caller's request.

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 short sentences, front-loaded with the action, with no filler. The second sentence is the only place where wording is slightly loose (it never connects inheritance back to the `inherited` parameter).

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 for a tool with zero annotation and zero schema-description coverage the definition is thin. An agent still lacks the meaning of the `inherited` parameter and any error or not-found behavior before calling it.

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 three parameters, so the description must compensate and largely does not. The `inherited` boolean is never explained despite being the parameter most likely to confuse an agent, and no id format or type expectations are given for the two required ids.

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?

States a specific verb and resource ("Retrieves a project dashboard") and adds scope nuance that the dashboard may live on the project or be inherited from a parent. It is clearly a single-resource fetch versus the sibling list tool, though it never names that sibling to make the contrast explicit.

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: nothing says when to fetch a single dashboard versus listing dashboards, no prerequisites, and no mention of what conditions (such as the inherited flag) change the call. The inheritance sentence describes the resource, not when an agent should pick this tool.

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