Skip to main content
Glama
jtauschl

OpenProject MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_instance_configuration

Retrieve instance-level OpenProject configuration and active feature flags so AI agents can verify available capabilities before acting.

Instructions

Return instance-level OpenProject configuration and active feature flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON 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?

No annotations are provided, so the description carries the full behavioral burden. 'Return' implies a safe read, and it discloses the returned content (configuration plus active feature flags), but it says nothing about auth/permission requirements, whether values are admin-scoped, caching, or rate limits.

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?

One short sentence, front-loaded with the action and the exact resource. No filler, no redundancy with the name.

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?

An output schema exists, so return values need no explanation here, and a zero-parameter getter has few hidden behaviors. The remaining gap is scope/eligibility - who can call it and what 'instance-level' covers - which is minor for a simple read.

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 the schema description baseline of 4 applies. There is nothing parameter-related for the description 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?

Specific verb ('Return') plus a well-scoped resource ('instance-level OpenProject configuration and active feature flags'), which is distinguishable from the sibling list_*/get_* entity lookups. It does not name those siblings, but the resource is narrow enough that confusion is unlikely.

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 statement or named alternatives. Usage is only implied by the name and the phrase 'instance-level configuration' - an agent can infer it is the tool for discovering available feature flags, but nothing tells it when this is preferable to other calls or what prerequisites exist.

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