Skip to main content
Glama
Sign In
mcp-gitlab-crunchtools

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Wiki Page Tool

create_wiki_page_tool

Creates a new wiki page in a GitLab project using project ID/path, title, and content; supports optional markdown, rdoc, asciidoc, or org format.

Instructions

Create a new wiki page in a GitLab project.

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": {
      "project_id": "<project_id>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_wiki_page_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPage title
formatNoContent format - markdown, rdoc, asciidoc, or org (default: markdown)markdown
contentYesPage content
project_idYesProject ID or path

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/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 the full burden of behavioral disclosure. It says 'create' but does not say what happens if a page with the same title already exists, whether content is overwritten, what permissions or access level are required, or how the page slug is derived — all material for a mutation tool.

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?

A single front-loaded sentence with no filler — the verb and resource lead immediately. It is terse to the point of under-specification, but nothing in it is wasted.

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?

An output schema exists, so return shapes need not be explained. However, for a four-parameter mutation tool with zero annotations, the description leaves out permissions, duplicate-title behavior, and error conditions that an agent would need to invoke it safely.

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?

Schema description coverage is 100%, so all four parameters (project_id, title, content, format) are already documented in the schema including the format enum values and default. The description adds no parameter meaning beyond that, which is acceptable at the baseline but not additive.

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 specific verb and resource (create a wiki page) scoped to a GitLab project, which cleanly separates it from get_wiki_page_tool and list_wiki_pages_tool by operation type. It does not explicitly name a sibling or contrast behavior, so it stops short of 5.

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 versus alternatives, nor any prerequisite context (e.g., whether the wiki must be enabled on the project). The description is a bare statement of capability with no usage framing.

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