Skip to main content
Glama

list_boards

Read-onlyIdempotent

Lists saved OpenProject boards and queries, optionally scoped to a project or filtered by search. Page through results until next_offset is null to collect every accessible board.

Instructions

List saved OpenProject boards/queries, optionally scoped to a project.

With project, search, or a restrictive OPENPROJECT_READ_PROJECTS, total is only the count of allowed boards returned on THIS page, not a full count of all matches; the search stops as soon as it has enough, so an exact total would need an extra full walk. Page until next_offset is null.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, capped at OPENPROJECT_MAX_PAGE_SIZE.
offsetNo1-based page number; pass the previous result's next_offset.
searchNo
selectNoFields to return; a requested unset field comes back as null. Allowed: can_delete, can_update, filter_count, hidden, id, include_subprojects, name, project, project_id, public, show_hierarchies, starred, timeline_visible.
projectNoProject identifier, id, or name; a unique part of a name or identifier also matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4
  2. Removedv0.4.0
  3. Changed1 schema field changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv0.3.3
  5. Removedv0.3.0
  6. Changed1 schema field changedv0.2.3
    • changedOutput schema / (root)
      Previous value: -{
      -  "$defs": {
      -    "BoardSummary": {
      -      "properties": {
      -        "can_delete": {
      -          "title": "Can Delete",
      -          "type": "boolean"
      -        },
      -        "can_update": {
      -          "title": "Can Update",
      -          "type": "boolean"
      -        },
      -        "filter_count": {
      -          "title": "Filter Count",
      -          "type": "integer"
      -        },
      -        "hidden": {
      -          "title": "Hidden",
      -          "type": "boolean"
      -        },
      -        "id": {
      -          "title": "Id",
      -          "type": "integer"
      -        },
      -        "include_subprojects": {
      -          "title": "Include Subprojects",
      -          "type": "boolean"
      -        },
      -        "name": {
      -          "title": "Name",
      -          "type": "string"
      -        },
      -        "project": {
      -          "anyOf": [
      -            {
      -              "type": "string"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ],
      -          "title": "Project"
      -        },
      -        "project_id": {
      -          "anyOf": [
      -            {
      -              "type": "integer"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ],
      -          "title": "Project Id"
      -        },
      -        "public": {
      -          "title": "Public",
      -          "type": "boolean"
      -        },
      -        "show_hierarchies": {
      -          "title": "Show Hierarchies",
      -          "type": "boolean"
      -        },
      -        "starred": {
      -          "title": "Starred",
      -          "type": "boolean"
      -        },
      -        "timeline_visible": {
      -          "title": "Timeline Visible",
      -          "type": "boolean"
      -        },
      -        "url": {
      -          "title": "Url",
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "id",
      -        "name",
      -        "project_id",
      -        "project",
      -        "public",
      -        "hidden",
      -        "starred",
      -        "include_subprojects",
      -        "show_hierarchies",
      -        "timeline_visible",
      -        "filter_count",
      -        "can_update",
      -        "can_delete",
      -        "url"
      -      ],
      -      "title": "BoardSummary",
      -      "type": "object"
      -    }
      -  },
      -  "properties": {
      -    "count": {
      -      "title": "Count",
      -      "type": "integer"
      -    },
      -    "limit": {
      -      "title": "Limit",
      -      "type": "integer"
      -    },
      -    "next_offset": {
      -      "anyOf": [
      -        {
      -          "type": "integer"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "title": "Next Offset"
      -    },
      -    "offset": {
      -      "title": "Offset",
      -      "type": "integer"
      -    },
      -    "results": {
      -      "items": {
      -        "$ref": "#/$defs/BoardSummary"
      -      },
      -      "title": "Results",
      -      "type": "array"
      -    },
      -    "total": {
      -      "title": "Total",
      -      "type": "integer"
      -    },
      -    "truncated": {
      -      "title": "Truncated",
      -      "type": "boolean"
      -    }
      -  },
      -  "required": [
      -    "offset",
      -    "limit",
      -    "total",
      -    "count",
      -    "next_offset",
      -    "truncated",
      -    "results"
      -  ],
      -  "title": "BoardListResult",
      -  "type": "object"
      -}New value: +null
  7. First observedv0.2.2

TDQS

A4.3/5.0
Behavior5/5

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

Adds genuinely non-obvious behavior beyond the readOnly/idempotent/openWorld annotations: the total field is a page-local count when project, search, or OPENPROJECT_READ_PROJECTS restricts results, because search stops early. This is exactly the kind of subtle return-value behavior an agent would otherwise misinterpret.

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?

Purpose sentence is front-loaded, followed by a dense but useful caveat and a paging instruction. The middle sentence is slightly convoluted ('total is only the count of allowed boards returned on THIS page, not a full count of all matches') but every sentence earns its place.

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?

With no output schema, the description carries the burden of explaining the return shape, and it does cover the key field (total) and the pagination sentinel (next_offset). It omits other return fields such as filter_count/starred that appear in select, but nothing blocking correct invocation is missing.

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 coverage is 80%, so the schema already documents limit, offset, select, and project. The description explains the downstream effect of project/search on the total count, which is meaning beyond the schema, but it adds nothing about the select or limit semantics themselves. Baseline 3 fits.

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 (list saved OpenProject boards/queries) and a clear scope modifier (optionally scoped to a project). The agent can distinguish it from get_board/create_board/update_board among siblings without opening any 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 concrete operational instructions: when a project/search/read restriction applies, the total is page-scoped, and the caller should page until next_offset is null. It does not explicitly name alternatives such as get_board for a single board, so it falls short of the 5 bar.

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