Skip to main content
Glama

search_tasks

Read-onlyIdempotent

Find tasks by text across server and visible local projects, including archived items, with status and project filters; returns task IDs for retrieval.

Instructions

Find tasks by text, the way Mizito's own search page does (server side, includes archived projects), merged with an exact local match on title/notes/checklist of visible projects. status "open" | "done" | "all". Optional project narrows the result. Returns ids for get_task.

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
limitNo
queryYes
offsetNo
statusNoopen
projectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the search reaches server-side results including archived projects, while the exact local match is limited to visible projects, and results are a merge of the two. It omits pagination behavior and what happens when the two sources disagree or overlap, which keeps it below a 5.

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?

Front-loaded with the core action and mechanism in the first sentence, with scoping details and the return-value handoff after. The telegraphic fragments ("status "open" | "done" | "all".") are dense but not padded; every clause carries information, though the sentence boundaries are choppy.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the annotations cover safety. What is missing is still material: no explanation of limit/offset or result-window behavior for a search that may return many matches, and no statement of the default status filter. Adequate but with clear gaps for a 5-parameter hybrid search tool.

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 description coverage is 0%, so the description must carry parameter meaning. It gives the semantics of query (text search), status ("open" | "done" | "all"), and project ("narrows the result"), but says nothing about limit or offset, leaving 2 of 5 parameters undocumented anywhere. Partial compensation for a low-coverage 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 and resource ("Find tasks by text") and goes further to describe the mechanism: server-side search of Mizito's own search index including archived projects, merged with an exact local match on title/notes/checklist of visible projects. It also names the natural follow-up ("Returns ids for get_task"). It does not explicitly contrast with list_tasks or list_my_tasks, so an agent must infer the split from the names alone.

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?

Usage is implied rather than stated: use it to locate tasks by text, optionally narrowing with project, then feed the returned ids to get_task. There is no explicit when-not guidance, no mention of how this differs from the sibling list_tasks, and no note that status defaults to "open" (only visible in the schema).

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