Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigservertasks

getConfigServerTasks

Lists background work-queue tasks the Gerrit daemon is currently performing or will perform soon, helping you monitor pending server activity.

Instructions

Lists the tasks from the background work queues that the Gerrit daemon is currently performing, or will perform in the near future.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getConfigServerTasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo

Output Schema

NameRequiredDescriptionDefault
resultNo

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?

With no annotations, the description carries the full behavioral burden, and it only clarifies what the listed items are (current and near-future queue entries). It says nothing about access restrictions, whether the queue view is global or per-node, pagination, or ordering, all of which matter for a server-administration endpoint.

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 well-formed sentence with no filler, and the key concept (background work queues) is front-loaded. It is efficient, though the space saved could have been spent on the state filter or access requirements.

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 restated, and the tool is simple with one optional parameter. Still, the undocumented state filter and the absence of any permission or scope context leave gaps an agent must fill by trial and error.

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% and the description never mentions the single 'state' parameter, so there is no explanation of what state values are accepted or how filtering works. An agent would have to guess at valid values and whether omitting the array means 'all states'.

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 uses a specific verb ('Lists') with a concrete resource ('tasks from the background work queues that the Gerrit daemon is currently performing, or will perform in the near future'). This clearly separates it from the sibling getConfigServerTasksTaskId, which fetches a single task, though the description never names that sibling explicitly.

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 mention of prerequisites such as admin permissions, and no routing to the singular getConfigServerTasksTaskId tool for detail lookups. The agent must infer that this is the enumeration tool and that one would call it before drilling into a specific task.

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