Skip to main content
Glama
Gerrit OpenAPI MCP

Gerrit OpenAPI MCP

by davido

Getaccountsaccountidactive

getAccountsAccountIdActive

Check whether a Gerrit account is active by providing its account ID, helping you verify account status before access or review actions.

Instructions

Checks if an account is active.

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": "getAccountsAccountIdActive"
  }
}

Input Schema

NameRequiredDescriptionDefault
account-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and delivers almost nothing: it does not say what "active" means (login enabled? not suspended? not blocked?), whether the result is a boolean or an object, or whether it requires privileged access. "Checks" implies a read, but nothing about failure modes or missing-account behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, so it is efficient, but the brevity comes at the cost of under-specification rather than tightness. Nothing is front-loaded beyond the bare claim.

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?

With no annotations, no output schema, and undocumented parameters, the description needs to define the returned value and the semantics of "active"; it does neither. An agent can form a rough guess but cannot confidently interpret or act on the result.

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?

There is one parameter, account-id, with 0% schema description coverage. The description implies the parameter's role but adds no meaning beyond the tool name, leaving unstated whether it accepts a numeric ID, a username, or a fully qualified identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Checks if an account is active" gives a specific verb and a resource, but "active" is not distinguished from the adjacent siblings getAccountsAccountIdState and getAccountsAccountIdStatus, so an agent cannot tell which of the three to call. The core operation is understandable, but the boundary is left blurry.

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 when-to-use guidance is given, no condition that selects this over the State or Status siblings, and no prerequisites. The agent is left to infer the use case entirely from the name.

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