Skip to main content
Glama
Sign In
OpenProject CE MCP

OpenProject CE MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_board

Saves an OpenProject work package query as a reusable board, including filters, columns, sorting, and grouping for repeatable project views.

Instructions

Create a saved OpenProject board/query.

This saves a work package query (filters, columns, sorting, grouping); a board grid that shows queries as columns is created with create_grid.

Input Schema

NameRequiredDescriptionDefault
nameYesBoard name, at most 255 characters.
hiddenNoIgnored by OpenProject; the value is not stored.
publicNoVisible to other users; false keeps it to its creator.
columnsNoColumn attribute ids (e.g. "id", "subject") or /api/v3/queries/columns/ hrefs.
confirmNofalse: preview only, nothing changes. true: applies it; get the user's approval of the preview first.
filtersNoOpenProject query filter objects, sent unchanged, e.g. {"_links": {"filter": {"href": "/api/v3/queries/filters/status"}, "operator": {"href": "/api/v3/queries/operators/o"}, "values": []}}.
projectNoProject identifier, id, or name; a unique part of a name or identifier also matches.
sort_byNoSort criteria, each "field:direction" or "field-direction" (e.g. "id:asc"), a bare field (ascending), or a /api/v3/queries/sort_bys/ href; the direction is case-insensitive.
starredNoMark as a favorite query.
group_byNoGroup-by attribute id (e.g. "status") or its /api/v3/queries/group_bys/ href.
show_hierarchiesNoShow parent/child tree; cannot combine with group_by, so it defaults to false there.
timeline_visibleNoShow the Gantt timeline.
include_subprojectsNoAlso show work packages of subprojects.
highlighted_attributesNoColumn ids or hrefs whose values are highlighted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, open-world write; the description adds meaningful context by clarifying that what is persisted is a query definition (filters, columns, sorting, grouping) rather than a grid layout. It does not surface the preview/confirm two-step or the fact that some inputs are ignored, but the schema documents both, so the gap is modest.

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, zero filler, with the core definition front-loaded and the sibling disambiguation second. The line break is cosmetic and does not hurt readability.

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 14-parameter mutation with no output schema, the description covers identity and routing, and the schema carries the rest. What is missing is the workflow-level context an agent needs before calling it: the preview-then-confirm approval loop and the permission implications of `public`.

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%, so every one of the 14 parameters is already documented in detail, including the ignored `hidden` flag and the confirm-preview semantics. The description only names the query attributes generically (filters, columns, sorting, grouping), which adds little beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ("Create a saved OpenProject board/query") and immediately defines what the resource actually is: a persisted work package query with filters, columns, sorting and grouping. It also explicitly separates itself from the sibling create_grid, so an agent can route correctly without opening either 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?

Gives an explicit alternative: if the intent is a board grid showing queries as columns, use create_grid instead. That is a real routing decision the agent would otherwise get wrong. It stops short of full when/when-not coverage (e.g. no mention of update_board for existing boards or permissions for public boards).

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