Skip to main content
Glama
Sign In
gitlab-api

gitlab-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get milestone

gitlab_get_milestone
Read-onlyIdempotent

Retrieve a specific project milestone by ID or title to view its details, state, and description for tracking project progress.

Instructions

Get a specific project milestone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_get_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
titleNo
project_idNo
descriptionNo
state_eventNo
milestone_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv27.3.13

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 known. The description adds no behavioral context beyond the bare purpose, such as authentication needs, error behavior, or what happens with optional parameters.

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?

It is a single front-loaded sentence with no wasted words. The terseness is efficient, though it leaves the definition under-specified for the tool's complexity.

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 tool with six optional parameters and no schema descriptions, the one-sentence description is not enough to tell an agent how to invoke it correctly. The annotations cover safety, but there is no guidance on which parameters to supply or what the tool returns.

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

Parameters1/5

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

The schema lists six parameters (data, title, project_id, description, state_event, milestone_id) with 0% description coverage and no required fields. The description mentions none of them, so an agent cannot tell which parameters identify the milestone or how they interact.

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 states a clear verb ('Get') and resource ('specific project milestone'), distinguishing it from the plural list tool by the word 'specific'. It does not explicitly name sibling alternatives such as get_milestones or update_milestone, so it falls short of full sibling differentiation.

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 guidance on when to use this tool versus get_milestones, update_milestone, or delete_milestone, and no prerequisites or exclusions are stated. The purpose implies retrieval, but the agent must infer all usage conditions.

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