Skip to main content
Glama
IDEAManagement

idea-base-mcp-server

Official
by IDEAManagement
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_tasks

Find tasks across projects by title or description, with optional filters for status, project, product, or customer. Results are ranked by relevance and show key fields for quick scanning.

Instructions

Search for tasks across all projects by title or description. Returns compact rows (id, title, status, priority, project_id, project_name, product_name, customer_name, estimated_minutes, time_logged, due_date, snippet) ranked with title matches first, then description matches, then recency. Pass verbose:true for full rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return. Default 20, capped at 100.
queryYesSearch query to match against task titles and descriptions
statusNoFilter results by status
verboseNoReturn full task rows instead of compact rows. Default false.
product_idNoRestrict results to this product
project_idNoRestrict results to this project
customer_idNoRestrict results to this customer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.3.0
    • addedInput schema / properties / customer_id
      Added value: +{
+  "description": "Restrict results to this customer",
+  "type": "number"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results to return. Default 20, capped at 100.",
+  "type": "number"
+}
    • addedInput schema / properties / product_id
      Added value: +{
+  "description": "Restrict results to this product",
+  "type": "number"
+}
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Restrict results to this project",
+  "type": "number"
+}
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "todo",
-  "in_progress",
-  "done"
-]New value: +[
+  "todo",
+  "in_progress",
+  "blocked",
+  "done"
+]
    • addedInput schema / properties / verbose
      Added value: +{
+  "description": "Return full task rows instead of compact rows. Default false.",
+  "type": "boolean"
+}
  2. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does a solid job: it discloses matching fields, output row shape, ranking order (title matches, then description, then recency), and the verbose option. It stops short of noting empty-result behavior or other edge cases, but the core behavioral contract is well communicated.

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?

Two sentences carry all essential information with no filler. The main purpose is front-loaded, and the second sentence packs output details, ranking, and the verbose switch into one efficient, readable unit. Every clause earns its place.

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?

Given no output schema, describing the exact compact row fields is essential and well handled. The description also covers ranking and the verbose toggle. The main gap is that 'full rows' fields are not enumerated and no usage recommendation is given for choosing between compact and verbose output, but the tool is still safely invocable.

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

Parameters4/5

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

The schema already covers all 7 parameters at 100%, so the baseline is 3. The description adds value beyond the schema by explaining how query matches are ranked and what verbose:true changes, which directly informs parameter usage. It does not repeat parameter descriptions, appropriately relying on 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 ('Search'), identifies the resource ('tasks'), and scopes the operation ('across all projects by title or description'). It also details the output format and ranking behavior, making the tool's purpose unmistakable even without inspecting the schema.

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 description clearly implies use for finding tasks by text across projects, and the 'across all projects' scope helps distinguish it from more narrow listing tools. However, it does not explicitly name any alternative sibling tool (e.g., list_tasks) or state when not to use this tool, leaving routing to inference.

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