Skip to main content
Glama
Sign In
Git MCP Server

Git MCP Server

by yumeminami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_milestones

Retrieve milestones for a project by specifying platform and project ID. Filter by state: active, closed, or all.

Instructions

List milestones for a project. State can be 'active', 'closed', or 'all'

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": {
      "platform": "<platform>",
      "project_id": "<project_id>"
    },
    "name": "list_milestones"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoactive
platformYes
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.1/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 full burden. It indicates a read operation but does not disclose potential side effects, auth requirements, rate limits, pagination, or any other behavioral traits beyond the state parameter values.

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?

Extremely concise with two sentences, front-loading the purpose and essential parameter info. Every word serves a purpose; no redundancy.

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 (3 params, 0% schema description, no annotations) and presence of an output schema, the description is too minimal. It fails to explain what milestones are, return format, or ordering, leaving gaps for an agent to use correctly.

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 coverage is 0%, so the description must add meaning. It only explains the 'state' parameter with allowed values. The 'platform' and 'project_id' parameters are not explained, leaving the agent to guess their purpose and how to obtain them.

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 clearly states the tool lists milestones for a project, which is a specific verb+resource. The sibling tool names include create, update, close, and list milestone variants, so this tool is well-differentiated as the list operation.

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 on when to use this tool versus alternatives like list_issues or list_merge_requests. It does not provide prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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