Skip to main content
Glama

Search tasks

search_tasks
Read-onlyIdempotent

Find tasks by text in the title (case-insensitive), e.g. "when is the dentist?" or before changing a task whose day you don't know. Searches from 30 days ago to a year ahead by default, the Backlog (tasks without a day, backlog: true), and repeating tasks (listed once with their schedule). Returns at most 50 results.

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
queryYesText to look for in task titles.
toDayKeyNoLast day to search (default: a year from today).
fromDayKeyNoFirst day to search (default: 30 days ago).
includeDoneNoInclude completed tasks (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the provided annotations (readOnly, idempotent), the description adds critical behavioral traits: the search is case-insensitive, it includes specific scopes like the Backlog and repeating tasks, and it imposes a hard limit of 50 results.

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 definition is highly dense with information but not verbose. Every sentence contributes specific scope, behavior, or usage context without unnecessary wording.

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 the complexity of a search function, the description is exceptionally complete, covering defaults, search methodology, and result limitations.

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?

While the schema coverage is 100%, the description adds vital semantic context that the schema lacks, such as defining 'the Backlog' as 'tasks without a day' and explaining how 'repeating tasks' are listed in the results.

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 provides a specific action ('Find tasks') and resource (tasks by text in title). It immediately clarifies the operational scope, which helps distinguish it from simple list or update siblings.

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

Usage Guidelines5/5

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

It provides a clear use case ('when is the dentist?') and defines its default search boundaries, making the guidance for use extremely specific and helpful.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources