Skip to main content
Glama
Sign In
taiga-mcp

taiga-mcp

by kiet0807
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List wiki pages

list_wiki_pages
Read-only

List wiki pages for a Taiga project, most recently changed first, to locate guides, conventions, and meeting notes kept outside user stories.

Instructions

List the wiki pages of a Taiga project, most recently changed first: slug, title, when it last changed and how long it is. The wiki holds what the team wrote down outside stories: guides, conventions, meeting notes. Read one page with get_wiki_page; to find pages by their text use search.

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

Input Schema

NameRequiredDescriptionDefault
pageNoWhich part of a long list, counted from 1. When an answer says more items exist, call again with the next page and the same `limit` and filters.
limitNoMost items to return in one answer (default 30, at most 100). The answer says how many more exist.
projectYesProject slug as given by list_projects, e.g. "acme-billing". Not the display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description still adds real context beyond them: the deterministic ordering, the returned field set, and what the wiki corpus actually contains (guides, conventions, meeting notes) rather than stories. It says nothing about result volume, but the schema's pagination parameters already explain that.

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

Conciseness5/5

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

Three sentences, front-loaded with the operation and ordering, then the routing guidance, then the domain framing. Every clause carries information; nothing is repeated from the schema.

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

Completeness5/5

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

With no output schema, enumerating the returned fields is the highest-value thing the description could do, and it does so. Pagination and the required project slug are handled by a fully documented schema, so nothing an agent needs to call this correctly is missing.

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%, with page, limit, and project each fully documented in-schema, including the slug-not-display-name caveat. The description adds no parameter meaning beyond what the schema states, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("List the wiki pages of a Taiga project") plus the ordering ("most recently changed first") and the fields returned (slug, title, last-changed, length). It also names the two siblings an agent might confuse it with, so the boundary is unambiguous.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives with their selecting condition: "Read one page with get_wiki_page; to find pages by their text use search." That covers both the single-item read case and the text-search case, leaving nothing to infer.

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