Skip to main content
Glama
Sign In
woodpecker-ci-mcp

woodpecker-ci-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a user

get_user
Read-onlyIdempotent

Fetch a specific user account from a forge by login. Requires admin access and the forge ID, which is available from list_users.

Instructions

Returns one account by its login. Admin only. forge_id is required — see list_users for the value.

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": {
      "login": "<login>",
      "forge_id": "<forge_id>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
loginYesThe account login as it is spelled in the forge.
forge_idYesWhich forge the login belongs to. Required by the API — a login is only unique per forge. list_users shows it; on a single-forge instance it is 1.
forge_remote_idNoDisambiguates further if the forge reuses logins.

Output Schema

NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the admin-only authorization requirement and notes that forge_id is needed by the API, which are behavioral details not present in the annotations.

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

Conciseness5/5

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

Two sentences, no filler. The core purpose is front-loaded, and the admin restriction and forge_id note are placed right after it. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only getter with a full output schema, 100% parameter schema coverage, and rich annotations, this description is complete. It tells the agent everything needed to call it correctly: the access level, the identifying parameters, and where to get the required forge_id.

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

Parameters4/5

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

Schema coverage is 100%, giving the baseline of 3. The description adds value by clarifying that forge_id is required by the API and that list_users is the source for its value, which helps an agent understand the relationship between parameters beyond the schema.

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

Purpose5/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 — 'Returns one account by its login' — and distinguishes itself from siblings by contrasting with list_users ('see list_users'). It makes the tool's scope immediately clear: fetch a single account, not a list.

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

Usage Guidelines4/5

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

The description gives clear usage context: 'Admin only' signals the permission boundary, and 'forge_id is required — see list_users for the value' tells the agent where to obtain a needed parameter. It doesn't explicitly state when to prefer this over get_current_user or list_users, but the singular-account framing makes the intended use unambiguous.

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