Skip to main content
Glama

get_wiki_pages

Read-onlyIdempotent

Lists all wiki pages in a CERN GitLab project or retrieves a specific page by slug, enabling access to project documentation stored in the repository wiki.

Instructions

Access wiki pages from a CERN GitLab repository. Can list all wiki pages or retrieve the content of a specific page. Useful for accessing project documentation that lives in the wiki.

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": "<project>"
    },
    "name": "get_wiki_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')
page_slugNoOptional: slug of a specific wiki page to retrieve. If omitted, lists all wiki pages.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / project / description
      Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')"
  2. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / page_slug / default
      Added value: +""
    • addedInput schema / properties / page_slug / title
      Added value: +"Page Slug"
    • changedInput schema / properties / project / description
      Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"
    • addedInput schema / properties / project / title
      Added value: +"Project"
    • addedInput schema / title
      Added value: +"get_wiki_pages_fnArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "get_wiki_pages_fnDictOutput",
      +  "type": "object"
      +}
  3. First observedv0.1.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered structurally. The description adds the mode-switching behavior (list vs. fetch) but says nothing about pagination of the list mode, whether a missing page_slug errors, authentication requirements, or wiki-disabled projects – all plausible failure modes for an openWorld 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?

Three short sentences, front-loaded with the resource and system before the mode options. The final sentence about documentation is mildly redundant with the second but does add a usage hint, so trimming is possible without being egregious.

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

Completeness4/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-value explanation is not required, and the annotations plus full schema coverage handle safety and parameters. What remains thin is guidance on list-mode volume and behavior for invalid slugs, but the definition is broadly sufficient for an agent to call it correctly.

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 coverage is 100% and the schema itself explains both the project identifier formats and the optional page_slug default-to-list behavior. The description merely restates that dichotomy in prose without adding format, slug syntax, or edge-case meaning, so the baseline 3 applies.

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 names a specific resource (wiki pages) in a specific system (CERN GitLab repository) and states the two modes: listing all pages or retrieving one page's content. It partially differentiates from siblings by scoping the resource to the wiki, though it never names get_project_readme or get_file_content as the non-wiki alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful for accessing project documentation that lives in the wiki' implies a usage context but gives no explicit when-to-use/when-not-to-use rule. With siblings like get_project_readme and get_file_content present, an agent would benefit from a statement such as 'use this only for content stored in the wiki, not for repository files' – that is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.