Skip to main content
Glama
Sign In
OpenProject CE MCP

OpenProject CE MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_board

Destructive

Modify a saved OpenProject board or query by changing selected fields; omitted fields remain unchanged, provided lists replace stored ones, and preview mode prevents changes until confirmed.

Instructions

Update a saved OpenProject board/query.

Omitted fields stay unchanged; a given list replaces the stored one.

Input Schema

NameRequiredDescriptionDefault
nameNoBoard 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.
board_idYesBoard (saved query) id, from list_boards.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true; the description adds one genuinely useful behavioral trait beyond them — that list fields are replaced wholesale rather than merged. However, it never mentions the preview/confirm approval gate defined in the schema, which is important for a destructive operation.

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 short sentences, front-loaded with what the tool does and immediately followed by the most consequential semantic. Nothing is padded.

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?

With 15 parameters and a destructive mutation profile, the description is thin: it covers the merge/replace rule but says nothing about the confirm-preview workflow, permission/auth expectations, or irreversibility. The rich schema compensates for parameter details, but the safety-critical context is left implicit.

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 100% so the baseline is 3, but the description goes beyond it by explaining how null/omitted parameters are treated (left unchanged) and how list parameters behave (replaced, not merged) — semantics the schema's `default: null` does not convey.

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?

States a specific verb and resource ("Update a saved OpenProject board/query"), which is distinct from create_board/delete_board/get_board siblings. It doesn't explicitly name those alternatives, but the operation is unambiguous.

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 gives no when-to-use or when-not-to-use guidance relative to create_board, update_grid, or execute_query. The only clause present (omitted fields unchanged) is a mutation semantic, not usage guidance.

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