Skip to main content
Glama
Sign In
OpenProject CE MCP

OpenProject CE MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_project_configuration

Read-onlyIdempotent

Retrieve a project's configuration, including instance settings and whether internal comments are enabled, by supplying a project ID, identifier, or name.

Instructions

Return a project's configuration: get_instance_configuration's fields plus enabled_internal_comments.

Input Schema

NameRequiredDescriptionDefault
projectYesProject identifier, id, or name; a unique part of a name or identifier also matches.

Output Schema

NameRequiredDescriptionDefault
project_idYes
project_nameYes
hours_per_dayYes
days_per_monthYes
duration_formatYes
per_page_optionsYes
available_featuresYes
trialling_featuresYes
active_feature_flagsYes
maximum_api_v3_page_sizeYes
enabled_internal_commentsYes
maximum_attachment_file_size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4
  2. Removedv0.4.0
  3. Changed3 schema fields changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / properties / url
      Removed value: -{
-  "title": "Url",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "project_id",
-  "project_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",
-  "enabled_internal_comments",
-  "url"
-]New value: +[
+  "project_id",
+  "project_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",
+  "enabled_internal_comments"
+]
  4. Addedv0.3.3
  5. Removedv0.3.0
  6. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and open-world access. The description adds only the return-field composition, without extra details on permissions, failure modes, or other behavioral context.

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?

The description is one compact, front-loaded sentence with no wasted wording.

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 a full parameter schema, an output schema, and rich annotations, the description supplies the key relationship to get_instance_configuration. The remaining gap is the lack of explicit usage guidance versus nearby project metadata tools.

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 100%, and the single project parameter is documented as accepting id, name, or partial match. The description adds no additional parameter meaning beyond the schema.

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?

The description uses a specific verb and resource: returns a project's configuration. It also distinguishes the tool from get_instance_configuration by stating it includes those fields plus enabled_internal_comments.

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?

The relationship to get_instance_configuration implies when this tool is useful, but it does not explicitly say when to choose this over get_project, get_project_admin_context, or get_instance_configuration itself.

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