Skip to main content
Glama

search_tasks

Read-only

Find Kanboard tasks using filter syntax across one or all projects, so you can locate work by status, assignee, due date, column, tag, or priority.

Instructions

Search tasks with Kanboard's filter syntax across one or all projects.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKanboard filter syntax, e.g. 'status:open assignee:me', 'due:<=today', 'column:"In progress"', 'tag:bug priority:3', or plain words to match titles.
project_idNoLimit to one project; omit to search all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-data nature is covered. The description adds nothing beyond that: no mention of result limits, pagination, or how broad a query may be, which matters for an open-world search.

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 front-loaded sentence with no redundant or filler wording; the scope constraint is stated immediately after the verb and resource.

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?

For a two-parameter read tool with full schema coverage, an output schema, and safety annotations supplied, nothing essential to correct invocation is missing. The only gap is sibling disambiguation, which is a guidance concern rather than a completeness one.

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 coverage is 100% and already documents both the query filter syntax with examples and the project_id scoping, so the schema does the heavy lifting. The description restates the single-vs-all-projects scope but adds no syntax or format detail beyond the schema.

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?

States a specific verb (search) and resource (tasks) plus the scope 'across one or all projects', and mentions Kanboard filter syntax which differentiates it from a plain enumerator like list_tasks. It stops short of naming the sibling it is not, so an agent has to infer the boundary.

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 phrase 'with Kanboard's filter syntax' implies this is the tool for filtered/queries rather than plain listing, but there is no explicit when-to-use or when-not guidance (e.g., versus list_tasks or get_overdue_tasks). Usage is implied, not stated.

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