Skip to main content
Glama
Sign In
backlog-mcp

backlog-mcp

by danglephuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sync Backlog Issues

sync-issues

Synchronizes Backlog issues into a local .tasks folder, converting them to markdown files for management in MCP-compatible editors.

Instructions

Sync issues from Backlog to local .tasks folder

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync-issues"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing side effects. It says 'Sync' but doesn't explain whether the operation overwrites files, deletes stale local tasks, is reversible, or what the impact on the local .tasks folder is.

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?

One short, front-loaded sentence conveys the action, source, and destination without any filler or redundant detail.

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 tool has no annotations, no output schema, and an empty input schema, so the description is the only operational guidance. It provides the basic action but leaves out critical sync behavior such as idempotency, conflict handling, and whether local files are modified destructively.

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?

The input schema is empty and there are zero parameters, so there is nothing to document. The baseline of 4 applies because no parameter semantics are needed.

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 names a specific operation ('Sync') and identifies the source and destination ('from Backlog to local .tasks folder'), making it easy to distinguish from siblings like get-issue or update-issues.

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?

The data flow direction implies a use case, but there is no explicit guidance about when to choose this tool over siblings such as bulk-create-tasks or update-issues, and no exclusion criteria are given.

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