Skip to main content
Glama
Sign In
OpenProject CE MCP

OpenProject CE MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_instance_configuration

Read-onlyIdempotent

Retrieves instance-level OpenProject configuration and active feature flags so agents can verify available settings and enabled capabilities before performing project actions.

Instructions

Return instance-level OpenProject configuration and active feature flags.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
host_nameYes
hours_per_dayYes
days_per_monthYes
duration_formatYes
per_page_optionsYes
available_featuresYes
trialling_featuresYes
active_feature_flagsYes
maximum_api_v3_page_sizeYes
maximum_attachment_file_size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • removedOutput schema / properties / maximum_attachment_file_size
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "title": "Maximum Attachment File Size"
-}
    • addedOutput schema / properties / maximum_attachment_file_size_bytes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Maximum Attachment File Size Bytes"
+}
    • changedOutput schema / required
      Previous value: -[
-  "host_name",
-  "maximum_attachment_file_size",
-  "maximum_api_v3_page_size",
-  "per_page_options",
-  "duration_format",
-  "hours_per_day",
-  "days_per_month",
-  "active_feature_flags",
-  "available_features",
-  "trialling_features"
-]New value: +[
+  "host_name",
+  "maximum_attachment_file_size_bytes",
+  "maximum_api_v3_page_size",
+  "per_page_options",
+  "duration_format",
+  "hours_per_day",
+  "days_per_month",
+  "active_feature_flags",
+  "available_features",
+  "trialling_features"
+]
  2. Changed1 schema field changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.3.3
  4. Removedv0.3.0
  5. First observedv0.2.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description adds that the response includes active feature flags, which is minor content disclosure; it says nothing about permissions needed, caching, or scope of exposure for an openWorld read.

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?

A single front-loaded sentence with no filler; the resource and scope appear before the payload detail.

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 zero parameters, an existing output schema, and annotations covering the safety profile, the description is sufficient to call the tool correctly. A note on what 'instance configuration' encompasses would make it fully self-contained.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and no schema gap to compensate for.

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 ("Return instance-level OpenProject configuration") plus the payload (feature flags). The qualifier "instance-level" effectively separates it from the sibling get_project_configuration, though the sibling is never named explicitly.

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?

No explicit when-to-use or when-not-to-use guidance; the contrast with project-scoped configuration must be inferred from the word "instance-level". Adequate for a zero-argument read, but nothing tells the agent when to prefer it over get_project_configuration or get_current_user.

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