Skip to main content
Glama

search_work_packages

Query work packages by free text, refined by project, status, assignee, priority, or dates. Tailor results with sorting, grouping, and field selection.

Instructions

Search work packages by free text, optionally scoped to a project.

Set status to restrict results to a specific OpenProject status. Set open_only=true to return only open work packages. Set assignee_me=true to return only work packages assigned to the current user.

assignee filters by any user (username, id, or "me"). assignee_me takes precedence.

priority filters by priority name or numeric ID (case-insensitive).

Date filters accept YYYY-MM-DD format:

  • created_on/updated_on/due_on: exact date match

  • created_between/updated_between/due_between: inclusive date range [start, end] Cannot specify both _on and _between for the same field.

sort_by accepts a list of sort criteria in format "field:direction" (e.g., ["status:desc", "priority:asc"]). Direction defaults to "asc" if omitted. Common sortable fields: id, subject, status, priority, type, assignee, author, created_at, updated_at, start_date, due_date.

group_by accepts a field name to group results by (e.g., "status", "assignee"). Common groupable fields: status, priority, type, assignee, author, version, category.

select restricts each result row to the given fields (e.g. ["id", "subject", "status"]); an invalid name returns the allowed set. Common fields: id, display_id, subject, type, status, priority, assignee, project, version, parent_id, start_date, due_date, estimated_time, spent_time, created_at, updated_at, author, category, description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
due_onNo
offsetNo
selectNo
statusNo
projectNo
sort_byNo
assigneeNo
group_byNo
priorityNo
open_onlyNo
created_onNo
updated_onNo
assignee_meNo
due_betweenNo
created_betweenNo
updated_betweenNo
Behavior4/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It thoroughly explains parameter precedence (assignee_me takes precedence), date filter exclusivity (cannot specify both _on and _between), default sort direction, and formatting requirements. It does not explicitly state that the tool is read-only, but the search context strongly implies it. The description adds substantial behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, with the purpose front-loaded in the first sentence, followed by logical parameter groupings. It is somewhat lengthy (8 paragraphs) but every section adds value; no superfluous content. Could be slightly more concise, but the organization aids understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 18 parameters, 0% schema coverage, and no output schema, the description is comprehensive. It covers all parameters, their constraints, and usage examples (e.g., date format, sort_by format). It explains grouping and selecting clearly. The description is complete for an agent to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate fully. It provides detailed semantics for nearly all 18 parameters: query, status, open_only, assignee_me, assignee, priority, date filters (format and exclusivity), sort_by, group_by, and select. It explains interactions, defaults, and allowed values, adding meaning that the input schema alone lacks.

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 clearly states 'Search work packages by free text, optionally scoped to a project.' This provides a specific verb (search), resource (work packages), and unique capability (free text searching with optional project scope). It effectively distinguishes the tool from sibling tools like get_work_package (single retrieval) and list_work_packages (listing without search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives like list_work_packages or get_work_package. It lacks when-not-to-use instructions or comparisons with sibling tools. The context is implied by the search functionality, but no direct guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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