Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidagreements

getAccountsAccountIdAgreements

Retrieves signed contributor agreements for a given Gerrit account ID so you can verify which agreements the user has accepted.

Instructions

Gets a list of the user's signed contributor agreements.

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": {
      "account-id": "<account-id>"
    },
    "name": "getAccountsAccountIdAgreements"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. The word 'Gets' implies a read operation and 'signed' hints at filtering, but nothing is said about permissions required, whether account-id must match an admin/self scope, pagination, or whether unsigned/pending agreements are excluded or included.

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 tightly written sentence with the resource front-loaded and no filler. It is perhaps overly terse for a tool with zero annotation coverage, but nothing is wasted.

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, and the tool is simple with one parameter. Still, the absence of annotations and of any parameter or scope detail leaves real gaps: an agent cannot confirm read-only safety, permission requirements, or result-set behavior from this description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single account-id parameter, so the description must compensate. The phrase 'the user's' weakly signals that account-id identifies whose agreements are returned, but it never states the expected format (numeric ID vs username) or whether it must be the caller's own account.

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: 'Gets a list of the user's signed contributor agreements.' The resource ('contributor agreements') is unique enough among siblings like getAccountsAccountIdGpgkeys or getAccountsAccountIdSshkeys to disambiguate, though the description does not explicitly name any sibling.

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 or when-not-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the resource name alone that this is the endpoint for agreements rather than for keys, tokens, or profile data.

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