Lists all available work package priorities so you can see valid priority levels for classifying tasks.
List all available work package priorities.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": {
- "PrioritySummary": {
- "properties": {
- "color": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Color"
- },
- "id": {
- "title": "Id",
- "type": "integer"
- },
- "is_active": {
- "title": "Is Active",
- "type": "boolean"
- },
- "is_default": {
- "title": "Is Default",
- "type": "boolean"
- },
- "name": {
- "title": "Name",
- "type": "string"
- },
- "position": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "title": "Position"
- }
- },
- "required": [
- "id",
- "name",
- "is_default",
- "is_active",
- "color",
- "position"
- ],
- "title": "PrioritySummary",
- "type": "object"
- }
- },
- "properties": {
- "count": {
- "title": "Count",
- "type": "integer"
- },
- "results": {
- "items": {
- "$ref": "#/$defs/PrioritySummary"
- },
- "title": "Results",
- "type": "array"
- }
- },
- "required": [
- "count",
- "results"
- ],
- "title": "PriorityListResult",
- "type": "object"
-}New value: +nullv0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It clearly indicates a read-only listing operation, but it does not disclose any additional behavioral details such as response format, sorting, or whether it includes all fields. However, for a simple list tool, this might be sufficient.
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?
A single, short sentence that is perfectly concise and front-loaded with the purpose.
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?
For a tool with no parameters and no output schema, the description is complete enough. It states the action and scope ('all available') without needing extra detail. It could mention the response format, but it's a simple list tool.
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 tool has zero parameters, and schema coverage is 100% (trivially). The description adds nothing beyond the schema because there are no parameters to explain. Baseline for high coverage is 3.
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 and resource: 'List all available work package priorities.' It uses a specific verb and resource, and it distinguishes from siblings like get_priority by indicating it lists all priorities rather than fetching a specific one.
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?
The tool's purpose is obvious from the name and description, but it does not explicitly mention when to use it over alternatives like get_priority. The usage context is implied, but no explicit guidance on choosing between tools is provided.
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