list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds context about default filtering to active subscriptions and lists specific return fields, which is helpful but not critical.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words, and front-loaded with the core action and return fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description explicitly lists all return fields. It also covers default behavior and the optional parameter, providing complete context for the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter 'include_inactive' is fully described in the schema. The description does not add additional meaning beyond stating it returns active subscriptions by default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool lists the caller's active subscriptions and specifies the returned fields. It distinguishes from sibling tools like subscribe and unsubscribe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises using this tool to review monitoring before adding more subscriptions or to find an id to cancel, providing clear context for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The vast majority of tools are unrelated to GitLab and cover overlapping domains (multiple ask_pipeworx variants, several Polymarket tools, memory tools). Only three GitLab-specific tools exist, and they are distinct from each other, but overall the set is highly heterogeneous and ambiguous.
Tool names use a mix of conventions: some are snake_case (ask_pipeworx, search_issues), some are compound nouns (get_project, list_subscriptions), and a few are single words (forget, recall). There is no consistent pattern, making it harder to predict tool names.
Despite the server name 'Gitlab Public', only 3 out of 34 tools are related to GitLab. The remaining 31 tools are a collection of unrelated services (Pipeworx data retrieval, Polymarket betting, memory, AI visibility). This is a severe mismatch between the server's stated purpose and its tool composition.
For a GitLab public server, essential tools like project creation, deletion, user management, and merge request handling are completely missing. The Pipeworx tools, while numerous, lack a clear cohesive scope and overlap significantly with each other.