Skip to main content
Glama
jtauschl

OpenProject MCP

by jtauschl
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_capabilities

Check which OpenProject API capabilities are available for a given project or capability ID, with pagination and access controls enforced.

Instructions

List API capabilities exposed by OpenProject.

At least one of project or capability_id is required — there is no unfiltered global listing, since one would bypass the project read allowlist.

limit is capped at OPENPROJECT_MAX_PAGE_SIZE (default 50); pass the returned next_offset as the next call's offset to page past the cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
projectNo
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.3.3
  3. Removedv0.3.0
  4. Changed1 schema field changedv0.2.3
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "CapabilitySummary": {
-      "properties": {
-        "action_id": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Action Id"
-        },
-        "action_name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Action Name"
-        },
-        "context": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Context"
-        },
-        "id": {
-          "title": "Id",
-          "type": "string"
-        },
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Name"
-        },
-        "principal_id": {
-          "anyOf": [
-            {
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Principal Id"
-        },
-        "principal_name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Principal Name"
-        },
-        "url": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Url"
-        }
-      },
-      "required": [
-        "id",
-        "name",
-        "action_id",
-        "action_name",
-        "principal_id",
-        "principal_name",
-        "context",
-        "url"
-      ],
-      "title": "CapabilitySummary",
-      "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/CapabilitySummary"
-      },
-      "title": "Results",
-      "type": "array"
-    },
-    "total": {
-      "title": "Total",
-      "type": "integer"
-    },
-    "truncated": {
-      "title": "Truncated",
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "offset",
-    "limit",
-    "total",
-    "count",
-    "next_offset",
-    "truncated",
-    "results"
-  ],
-  "title": "CapabilityListResult",
-  "type": "object"
-}New value: +null
  5. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the required-filter constraint, the pagination cap, and how to page via next_offset. It does not mention authentication or output details, but the core behavioral traits are disclosed.

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?

Three short paragraphs, front-loaded with the core purpose, and every sentence adds value. The pagination and filter constraints are presented efficiently without repetition or filler.

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?

Given the tool's complexity, the description covers the critical invocation constraints: required filters, the no-global-listing rule, and pagination. There is no output schema to lean on, and the description only hints at the return shape via next_offset, but an agent has enough to call the tool correctly.

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 0%, so the description must compensate. It meaningfully explains limit and offset behavior and the requirement for project/capability_id. However, it does not clarify the expected value formats or the relationship between project and capability_id, leaving some parameter semantics under-specified.

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 ('List API capabilities exposed by OpenProject') and is immediately understandable. It does not explicitly differentiate from similar sibling tools like list_actions or list_roles, but the resource scope is clear enough for an agent to identify the tool's purpose.

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?

Provides important invocation guidance: at least one of project or capability_id is required, and explains why unfiltered listing is not allowed. However, it does not say when to prefer this tool over alternatives, so usage context is only implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jtauschl/openproject-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server