Skip to main content
Glama
Sign In
taiga-mcp

taiga-mcp

by kiet0807
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read one wiki page

get_wiki_page
Read-only

Read a Taiga project wiki page by slug or title, returning its text plus who last changed it and when.

Instructions

Read the text of one wiki page of a Taiga project, with who changed it last and when. Name the page by its slug from list_wiki_pages or search, or by its title in the wiki menu.

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>",
      "page": "<page>"
    },
    "name": "get_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesSlug of the page, e.g. "home", or its title in the wiki menu.
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.4/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 adds that the response carries page text plus last-editor and timestamp metadata. That is meaningful extra context given there is no output schema. It stops short of saying what format the text is in or what happens when the slug is unknown.

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?

Two sentences, front-loaded with what is read and returned, followed by the naming rule. No filler, no restatement of the title or parameter types.

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?

For a simple two-parameter read with no output schema, the description covers purpose, identifier sourcing, and the shape of the returned data. Minor gaps remain around text format and not-found behavior, but nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds provenance the schema lacks: where to obtain the slug and that a wiki-menu title is equally acceptable for 'page'. It also reinforces that 'project' is a slug rather than a display name, which matches the schema's own warning.

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?

The description states a specific verb and resource ('Read the text of one wiki page of a Taiga project') and even previews the payload ('who changed it last and when'). The word 'one' implicitly separates it from the sibling list_wiki_pages, so an agent can pick the right tool without opening a schema.

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

Usage Guidelines4/5

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

It tells the agent where to get the page identifier — 'slug from list_wiki_pages or search, or by its title in the wiki menu' — which is actionable routing guidance toward two named siblings. It does not state an explicit exclusion or failure case, but the single-page scope makes the list-vs-read distinction clear.

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