Get the work-package categories available in a project, helping you identify and use the correct category labels when creating or filtering work packages.
List work-package categories configured for a project.
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.3.7Input schema / additionalPropertiesAdded value: +falsev0.3.3v0.3.0v0.2.3Output schema / (root)Previous value: -{
- "$defs": {
- "CategorySummary": {
- "properties": {
- "id": {
- "title": "Id",
- "type": "integer"
- },
- "is_default": {
- "title": "Is Default",
- "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"
- },
- "url": {
- "title": "Url",
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "project_id",
- "project",
- "is_default",
- "url"
- ],
- "title": "CategorySummary",
- "type": "object"
- }
- },
- "properties": {
- "count": {
- "title": "Count",
- "type": "integer"
- },
- "results": {
- "items": {
- "$ref": "#/$defs/CategorySummary"
- },
- "title": "Results",
- "type": "array"
- }
- },
- "required": [
- "count",
- "results"
- ],
- "title": "CategoryListResult",
- "type": "object"
-}New value: +nullv0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits, but it only states the verb 'List' without detailing side effects, permissions, or response characteristics, leaving behavioral expectations vague.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that places the verb upfront, making it efficient and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is adequate for a simple list operation with one parameter, but it lacks any mention of output format, error behavior, or additional context that might be needed without annotations or an output schema, leaving some gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description minimally explains that the 'project' parameter identifies the project for which categories are listed, but it does not clarify whether it expects an ID, name, or other identifier, offering limited added meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (List) and the specific resource (work-package categories) within the context of a project, distinguishing it from sibling list tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No information is provided about when to use this tool versus alternatives, nor are any conditions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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