Skip to main content
Glama
Sign In

Decknote

by app.decknote
OverviewDiscussionsAdmin

Search tasks

search_tasks
Read-only

Searches the user's tasks (cards) across boards by free text in title and description, and by board, list, status (open, completed, all or archived) and due date. Answers questions like what is still open, what was noted about something, or what is due soon.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1–100. Default 20.
queryNoFree text; matches card title and description.
listIdNo
statusNoDefault 'open'. 'archived' finds archived tasks.
boardIdNo
includeNoExtra fields on each task. 'location' adds the names of its board (board) and list (list).
dueBeforeNoISO 8601; only tasks due before this instant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Extra fields on each task. 'location' adds the names of its board (board) and list (list).",
+  "items": {
+    "enum": [
+      "location"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"Default 'open'. 'archived' finds archived tasks (restore them with restore_task)."New value: +"Default 'open'. 'archived' finds archived tasks."
  3. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Default 'open'."New value: +"Default 'open'. 'archived' finds archived tasks (restore them with restore_task)."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "open",
-  "completed",
-  "all"
-]New value: +[
+  "open",
+  "completed",
+  "all",
+  "archived"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds search scope and filter semantics but does not disclose return behavior such as pagination, result ordering, default limits, or empty-result handling. The added context is useful but limited beyond what annotations provide.

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?

The description is two sentences and front-loads the core purpose before adding usage examples. Every clause earns its place by specifying the search dimensions or answering what questions the tool can resolve.

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 seven optional parameters, no output schema, and annotations that cover safety, the description covers the main search inputs and use cases well. It omits minor operational details such as the default limit and pagination behavior, but those are either in the schema or less critical for selecting the tool.

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?

Schema coverage is 71%, and the description adds meaning for key filters: 'free text in title and description', 'by board, list, status (open, completed, all or archived) and due date'. This compensates for the undescribed boardId and listId parameters. It does not discuss limit or include, but those are documented in 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?

The description gives a specific verb and resource: 'Searches the user's tasks (cards) across boards'. It also enumerates the search dimensions (free text, board, list, status, due date). It does not explicitly name a sibling tool or explain how it differs from `search` or `list_my_tasks`, so it falls just short of a 5.

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

Usage Guidelines4/5

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

It provides clear usage context through examples: 'Answers questions like what is still open, what was noted about something, or what is due soon.' This tells an agent when the tool is appropriate. However, it does not name alternatives or state when not to use it.

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

All Decknote toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources