Skip to main content
Glama
Sign In
gitlab-api

gitlab-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get namespaces

gitlab_get_namespaces
Read-onlyIdempotent

Retrieve GitLab namespace information and filter by search, ownership, top-level status, or ID to identify groups and users for access and project organization.

Instructions

Get information about namespaces.

Args: **kwargs: Additional parameters for the request (e.g., per_page).

Returns: Response: A wrapper containing the original response and a list of Namespace models.

Raises: ParameterError: If invalid parameters are provided.

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_namespaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
searchNo
max_pagesNo
owned_onlyNo
namespace_idNo
top_level_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv27.3.20
    • removedInput schema / properties / api_parameters
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • addedInput schema / properties / max_pages
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. First observedv27.3.13

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add value by disclosing the return wrapper containing a list of Namespace models and the ParameterError failure mode, but says nothing about pagination behavior despite a max_pages parameter.

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 docstring boilerplate (Args/Returns/Raises) is reasonably compact and the Returns section is useful, but the Args block is both inaccurate and wasted space given the real schema. Nothing is front-loaded to help an agent decide between this and the singular get tool.

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 six-parameter, zero-coverage, no-output-schema tool, the description is far too thin: none of the filter semantics (search, owned_only, top_level_only, namespace_id) are explained, and the parameter guidance it does give contradicts the schema. Only the return type and error case are adequately covered.

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% across six parameters (search, owned_only, top_level_only, namespace_id, max_pages, data), so the description carries the full burden and fails. Worse, its only parameter text — "**kwargs: Additional parameters for the request (e.g., per_page)" — is stale and misleading, since the schema sets additionalProperties=false and defines no per_page field.

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?

"Get information about namespaces" names a resource and a read action, but it is generic about scope — it does not say whether it lists all namespaces, filters them, or returns a single one. The sibling gitlab_get_namespace (singular) exists, and the description gives no cue to distinguish the plural list tool from it.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as gitlab_get_namespace or gitlab_get_groups. The agent must infer from the plural name alone that this is the enumeration tool.

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