Skip to main content
Glama
nulab

Backlog MCP Server

get_wiki

Retrieve detailed information about a specific wiki page using its ID. Optionally specify an organization to scope the query.

Instructions

Returns information about a specific wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiIdYesWiki ID
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The main handler function for the 'get_wiki' tool. It defines the tool name, description, input schema (wikiId), output schema (WikiSchema), and the handler that converts wikiId to a number and calls backlog.getWiki().
    export const getWikiTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getWikiSchema>,
      (typeof WikiSchema)['shape']
    > => {
      return {
        name: 'get_wiki',
        description: t(
          'TOOL_GET_WIKI_DESCRIPTION',
          'Returns information about a specific wiki page'
        ),
        schema: z.object(getWikiSchema(t)),
        outputSchema: WikiSchema,
        importantFields: ['id', 'projectId', 'name', 'content'],
        handler: async ({ wikiId }) => {
          const wikiIdNumber =
            typeof wikiId === 'string' ? parseInt(wikiId, 10) : wikiId;
          return backlog.getWiki(wikiIdNumber);
        },
      };
    };
  • Input schema for the 'get_wiki' tool, defining a required 'wikiId' parameter that accepts either a string or a number.
    const getWikiSchema = buildToolSchema((t) => ({
      wikiId: z
        .union([z.string(), z.number()])
        .describe(t('TOOL_GET_WIKI_ID', 'Wiki ID')),
    }));
  • Output schema (WikiSchema) for the wiki object returned by get_wiki, containing fields like id, projectId, name, content, tags, attachments, etc.
    export const WikiSchema = z.object({
      id: z.number(),
      projectId: z.number(),
      name: z.string(),
      content: z.string(),
      tags: z.array(TagSchema),
      attachments: z.array(WikiFileInfoSchema),
      sharedFiles: z.array(SharedFileSchema),
      stars: z.array(StarSchema),
      createdUser: UserSchema,
      created: z.string(),
      updatedUser: UserSchema,
      updated: z.string(),
    });
  • Registration of get_wiki in the 'wiki' toolset group within the allTools registry, alongside other wiki tools.
    {
      name: 'wiki',
      description: 'Tools for managing wiki pages.',
      enabled: false,
      tools: [
        getWikiPagesTool(backlog, helper),
        getWikisCountTool(backlog, helper),
        getWikiTool(backlog, helper),
        addWikiTool(backlog, helper),
        updateWikiTool(backlog, helper),
      ],
    },
  • The buildToolSchema helper used by get_wiki to create its input schema definition.
    export const buildToolSchema = <T extends z.ZodRawShape>(
      fn: (t: TranslationHelper['t']) => T
    ) => fn;
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, required permissions, or rate limits. It merely states the basic function.

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?

The description is a single clear sentence with no unnecessary words. It is appropriately sized and front-loaded, though it could potentially add more value without sacrificing brevity.

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

Completeness3/5

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

Given the simplicity of the tool and lack of output schema, the description is minimally adequate. However, it lacks details on what information is returned or any return format expectations.

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% with both parameters described. The description adds no additional meaning beyond the schema's parameter descriptions, so it meets the baseline but does not exceed.

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 clearly states it returns information about a specific wiki page, differentiating it from sibling tools like get_wiki_pages which returns a list. The verb 'returns' and resource 'wiki page' are specific.

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?

No guidance on when to use this tool versus alternatives like get_wiki_pages, and no mention of prerequisites or context where it should be preferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nulab/backlog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server