Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidemailsemailid

getAccountsAccountIdEmailsEmailId

Retrieve a user's email address from Gerrit by account ID and email ID.

Instructions

Retrieves an email address of a user.

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>",
      "email-id": "<email-id>"
    },
    "name": "getAccountsAccountIdEmailsEmailId"
  }
}

Input Schema

NameRequiredDescriptionDefault
email-idYes
account-idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations supplied, "Retrieves" only implies a read operation and provides no explicit safety, permission, or error behavior. It does not explain what happens for unknown or inaccessible identifiers, although the presence of an output schema reduces the need to describe the response structure.

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?

The single sentence is front-loaded, grammatical, and free of filler. However, its brevity omits information needed for reliable selection and invocation, so it is not fully effective structure.

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?

For a simple two-identifier getter with an output schema, the basic purpose is covered, but the invocation context is not. The absence of annotations and parameter documentation makes the missing identifier semantics, access expectations, and endpoint-selection guidance significant gaps.

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 only indirectly suggests that account-id scopes the user and email-id selects an address. It never explicitly defines either required identifier, its accepted form, or where the agent can obtain it.

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 clear verb and resource: "Retrieves an email address of a user." It does not clarify that the address belongs to the specified account and is selected by email-id, nor does it distinguish this item endpoint from related account/email endpoints.

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 explicit guidance about when to use this tool, what identifiers must be obtained first, or when a related endpoint might be preferable. In particular, it does not explain the choice between this operation and getAccountsAccountIdEmails, leaving selection largely to inference from the tool names.

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