Skip to main content
Glama
Sign In
backlog-mcp-server

backlog-mcp-server

by mcpflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

backlog_get_wiki

Retrieve a specific Wiki page from Backlog using its page ID.

Instructions

Performs an wiki get using the Backlog Wiki API.

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": {
      "wikiId": "<wikiId>"
    },
    "name": "backlog_get_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiIdYesWiki page ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, authentication requirements, or side effects. The description fails to inform the agent about what happens when this tool is invoked.

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

Conciseness3/5

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

The description is very concise, only one sentence. However, it does not fully utilize the space to provide helpful context; it is minimally sufficient but not earnestly helpful.

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?

The description is incomplete for a tool with no output schema. It does not indicate what the tool returns (e.g., wiki page content, metadata), nor does it address possible errors or access requirements. Given low complexity, more detail is expected.

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% for the single parameter 'wikiId', with its own description 'Wiki page ID'. The description adds no additional meaning beyond the schema, but since coverage is high, baseline score is appropriate.

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 'Performs a wiki get' which implies retrieving a single wiki page. Given the required wikiId parameter and sibling tool backlog_get_wikis for listing, the purpose is reasonably clear, though it could be more precise about what is retrieved.

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?

The description provides no guidance on when to use this tool versus alternatives like backlog_get_wikis or other tools. No context about prerequisites or exclusions.

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