Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getconfigservertaskstaskid

getConfigServerTasksTaskId

Retrieve a Gerrit background work queue task by ID to check work the daemon is currently performing or will perform soon.

Instructions

Retrieves a task from the background work queue that the Gerrit daemon is currently performing, or will perform in the near future.

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": {
      "task-id": "<task-id>"
    },
    "name": "getConfigServerTasksTaskId"
  }
}

Input Schema

NameRequiredDescriptionDefault
task-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does add useful domain context by explaining that a task is background work the daemon is performing or will soon perform. It says nothing about whether the call is read-only, whether tasks expire or get pruned, or how an unknown task id is reported, which for an un-annotated tool is a gap.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though brevity comes at the cost of the missing operational detail noted above.

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 described, and the description adequately frames what a task is. However, with an undocumented required parameter and no error or provenance guidance, an agent still lacks what it needs to obtain a valid id and interpret failures.

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?

The single task-id parameter has 0% schema description coverage, so the description is the only source of meaning and it never explains the id's format, source, or scope. A caller learns only indirectly that the value designates a queued task.

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 task") and scopes it to the Gerrit daemon's background work queue, which distinguishes it from the plural list sibling getConfigServerTasks by the singular "a task". It never names the list endpoint as the way to discover IDs, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the singular "a task" plus the required task-id signals a fetch-one-by-identifier operation. There is no guidance on when to prefer this over getConfigServerTasks, no statement that the task id must come from the list endpoint, and no note on what happens for unknown ids.

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