Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by mcpland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Group Milestone

gitlab_get_group_milestone
Read-onlyIdempotent

Fetch a single GitLab group milestone using its group ID and milestone ID to view milestone details and status.

Instructions

Get one group milestone by its ID.

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": {
      "group_id": "<group_id>",
      "milestone_id": "<milestone_id>"
    },
    "name": "gitlab_get_group_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes
milestone_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond that – nothing about what happens when the milestone is not found, what the response contains, or permission requirements.

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?

The single sentence is front-loaded and free of waste, but its brevity comes at the cost of under-specification rather than efficiency. It reads as a minimal placeholder rather than a deliberately tight definition.

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 two-parameter lookup with zero schema description coverage and no output schema, the description should at least pin down the identifier formats and what a successful response looks like. Annotations carry the safety story, but the parameter and result semantics remain entirely undocumented.

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%, so neither group_id nor milestone_id is documented anywhere. The phrase 'by its ID' hints that milestone_id is an identifier, but it does not clarify whether that is a global milestone ID or a group-scoped iid, nor what form group_id takes (numeric ID or path).

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 gives a specific verb ('Get') and a scoped resource ('one group milestone'), and 'by its ID' indicates a single-record lookup. It does not explicitly distinguish this from the sibling gitlab_get_milestone (project-scoped) or from gitlab_list_group_milestones, so the reader must infer the distinction from the name alone.

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 statement of when to use this tool versus gitlab_list_group_milestones or the project-level gitlab_get_milestone, and no prerequisites or error conditions are mentioned. The only guidance is the implicit 'single record by ID' reading of the sentence.

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