BoardMark

Move an issue into a sprint, or to the backlog (sprint null). Scrum only.

move_to_sprint

Move an issue into a sprint, or to the backlog (sprint null). Scrum only.

Scrum projects only. sprint is a sprint id (S-3) or null for the backlog. Any planned or active sprint works (not a closed one); with several active sprints, use the one the user means.

WRITE: version = from your latest read (get_issue, list_comments, list_sprints, get_doc, read_file). 409 version_conflict (details.current, details.current_version): re-read, re-apply your change, retry — never overwrite blindly; when the changes disagree, ask the user.

Input Schema

Name	Required	Description
`reason`	No	Spec D144: why you make this change (≤ 200 characters). Optional, but give it when you act as an agent account — it is shown in the agent's run log ("moved KJ-12 To Do → In Progress because <reason>"). board-mcp records it in `agent.run`; board-core / board-files accept it and ignore it (it never changes the file, the version or the history).
`sprint`	Yes
`version`	Yes	Optimistic-lock version of the file; +1 on every write. Every write must send the version it read.
`issue_key`	Yes	Issue key `{PROJECT}-{n}`, e.g. `KJ-101`.
`project_key`	Yes	Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "Spec D144: why you make this change (≤ 200 characters). Optional, but give it when you act as an agent account — it is shown in the agent's run log (\"moved KJ-12 To Do → In Progress because <reason>\"). board-mcp records it in `agent.run`; board-core / board-files accept it and ignore it (it never changes the file, the version or the history).",
+  "maxLength": 200,
+  "type": "string"
+}

First observedOct 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it marks the operation as a WRITE, explains that version must come from the latest read, and describes the 409 version_conflict recovery flow. This is exactly the kind of concurrency and safety guidance an agent needs for a mutation tool.

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 reasonably compact and front-loads the main constraint and write behavior. However, it repeats the title almost verbatim and then repeats 'Scrum projects only' in the next paragraph, which is mild redundancy.

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?

For a Scrum-only mutation with no output schema, the description covers the essential constraints, nullable sprint behavior, optimistic-lock version requirement, and conflict recovery. Nothing critical for correct invocation appears to be 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 already high at 80%, and the description adds useful semantics for the most nuanced parameter: sprint is an S-n ID or null for backlog, and only planned or active sprints are valid. It also clarifies where version should come from.

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: moving an issue into a sprint or to the backlog, limited to Scrum projects. This is clearly distinguishable from sibling tools like update_sprint, close_sprint, and move_to_release.

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 gives meaningful conditions: Scrum projects only, sprint may be an ID or null for backlog, and closed sprints cannot be used. It does not explicitly name alternatives such as update_issue or move_to_release, but the usage context is otherwise clear.

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

All BoardMark tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?