Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by wisesky0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_namespaces

List GitLab namespaces with optional search filter and pagination. Supports specifying a GitLab instance.

Instructions

네임스페이스 목록 조회

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": "list_namespaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo페이지 번호 (1부터)
searchNo검색어 필터
instanceNo대상 GitLab 인스턴스명 (생략 시 default)
per_pageNo페이지당 개수 (기본 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It merely states it retrieves a list, without mentioning pagination, search, or instance selection parameters already defined in the schema. The description adds no behavioral context beyond the tool's basic function.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specified rather than efficiently concise. It repeats the tool's name without providing essential details, making it too brief to be useful for an AI agent.

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

Completeness1/5

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

The description is severely incomplete given the tool's complexity (4 parameters, no output schema). It fails to explain the scope of namespaces listed, the return format, or how it differs from closely related sibling tools like list_groups.

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

Parameters3/5

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

The input schema covers all four parameters with descriptions (page, search, instance, per_page), achieving 100% coverage. The description does not add any additional meaning to these parameters, so it meets the baseline expectation for this dimension.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '네임스페이스 목록 조회' is essentially a tautology of the tool name 'list_namespaces', restating the same idea without adding specificity. It does not distinguish the tool from siblings like list_groups, which also lists namespaces but more specifically for groups.

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 such as list_groups or list_projects. The description lacks any context about the tool's scope or filtering capabilities that would help an agent decide when to invoke it.

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