Skip to main content
Glama
hyperpolymath

BoJ-server

by hyperpolymath
OverviewSchemaRelated ServersScoreDiscussions

boj_gitlab_list_pipelines

Retrieve CI/CD pipeline status for a GitLab project to monitor build progress and deployment workflows.

Instructions

List CI/CD pipelines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • mcp-bridge/main.js:285-286 (handler)
    The handler implementation for the boj_gitlab_list_pipelines tool.
    case "boj_gitlab_list_pipelines":
  return gitlabApiCall("GET", `/projects/${encodeURIComponent(args.project_id)}/pipelines`);
  • mcp-bridge/main.js:557-562 (registration)
    Registration of the boj_gitlab_list_pipelines tool.
      { name: "boj_gitlab_list_pipelines", desc: "List CI/CD pipelines", props: { project_id: { type: "string" } }, req: ["project_id"] },
  { name: "boj_gitlab_setup_mirror", desc: "Set up a push mirror", props: { project_id: { type: "string" }, target_url: { type: "string" } }, req: ["project_id", "target_url"] },
];
for (const t of glTools) {
  tools.push({ name: t.name, description: t.desc, inputSchema: { type: "object", properties: t.props, required: t.req || [] } });
}

Tool Definition Quality

C2.6/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 of behavioral disclosure. 'List CI/CD pipelines' implies a read-only operation, but it doesn't specify critical details like authentication requirements, rate limits, pagination behavior, or what data is returned (e.g., pipeline statuses, IDs). This leaves significant gaps in understanding how the tool behaves in practice.

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?

The description is extremely concise with a single phrase, 'List CI/CD pipelines', which is front-loaded and wastes no words. While it may be too brief for completeness, it efficiently conveys the core action without unnecessary elaboration.

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?

Given the complexity of a CI/CD pipeline listing tool with no annotations, no output schema, and a parameter with 0% schema coverage, the description is incomplete. It doesn't address key aspects like return values, error handling, or operational constraints, making it inadequate for the agent to use the tool effectively without additional context.

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?

The input schema has one parameter ('project_id') with 0% description coverage, meaning the schema provides no semantic details. The description adds no information about parameters, failing to explain what 'project_id' represents (e.g., a GitLab project ID or name) or its format, which is insufficient given the low schema coverage.

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?

The description 'List CI/CD pipelines' clearly states the verb ('List') and resource ('CI/CD pipelines'), providing a basic understanding of the tool's function. However, it doesn't differentiate from sibling tools like 'boj_gitlab_list_issues' or 'boj_gitlab_list_mrs', which follow a similar pattern for different resources, making the purpose somewhat generic rather than specific.

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 provided on when to use this tool versus alternatives. The description lacks context such as prerequisites (e.g., authentication), when it's appropriate (e.g., for monitoring pipelines), or comparisons to other GitLab tools like 'boj_gitlab_list_projects', leaving the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hyperpolymath/boj-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server