Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getgroupsgroupidlogaudit

getGroupsGroupIdLogAudit

Retrieves the audit log for a specified Gerrit internal group by group ID, enabling review of group changes and administrative activity.

Instructions

Gets the audit log of a Gerrit internal group.

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": {
      "group-id": "<group-id>"
    },
    "name": "getGroupsGroupIdLogAudit"
  }
}

Input Schema

NameRequiredDescriptionDefault
group-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

There are no annotations, so the description carries the full disclosure burden. 'Gets' implies a read, but nothing is said about the permission requirements for audit-log access, whether results are paginated or time-ordered, or how far back the log reaches. Only the bare minimum of behavioral context is supplied.

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 short sentence with no filler and the resource front-loaded. It is efficient, though the brevity edges into under-specification rather than tightness.

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?

The tool is simple (one parameter, output schema present), so return values need not be explained. However, with no annotations and zero parameter documentation, the description should at least cover the permission prerequisite and accepted group-id formats; neither is addressed.

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 coverage is 0% for the single required 'group-id' parameter. The description only implies that the value identifies a group; it does not explain that Gerrit accepts a numeric ID, UUID, or group name, which is the key ambiguity an agent would face. It adds almost no meaning beyond the schema.

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 states a specific verb and resource: it 'Gets the audit log of a Gerrit internal group.' That is clearly distinct from the sibling getters (description, detail, members, owner, options), even though the description never names an alternative. It is clear but stops short of explicit sibling differentiation.

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?

No guidance is given on when to prefer this tool over getGroupsGroupIdDetail or the other group getters, and no preconditions are stated. Reading a Gerrit audit log typically requires elevated capability (e.g., administrator or View Audit Log), which the description does not mention at all.

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