Skip to main content
Glama

Coline

Search tasks

search_tasks
Read-onlyIdempotent

Searches tasks across the workspace's boards by meaning and keywords, optionally on one board.

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": {
      "workspace": "<workspace>",
      "query": "<query>"
    },
    "name": "search_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdNo

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description needn't restate safety. It does add scope behavior — search spans all workspace boards unless one board is named — but says nothing about ranking, result caps, or how semantic vs keyword matches are combined, which materially affects interpretation of results.

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?

A single tightly packed sentence with the resource and matching mode front-loaded and no filler. It borders on under-specification rather than verbosity, but nothing is wasted.

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?

With an output schema and full annotations present, the description covers the essentials of what is searched and where. It remains incomplete for a 4-parameter search tool in that it gives no sibling disambiguation and no guidance on query formulation or the shape of a scoped vs unscoped search.

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 only 25% (workspace is the sole documented property), so the description must compensate. It partially does, conveying that board scoping is optional and that the workspace bounds the search, but it never explains query semantics, the limit default/maximum, or the taskboardId parameter's format.

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?

Specific verb and resource: 'Searches tasks' scoped to 'the workspace's boards', with the useful detail that matching is both semantic ('by meaning') and lexical ('keywords'). It does not differentiate itself from close siblings such as filter_tasks or list_tasks, so an agent must 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?

Usage is only implied: 'by meaning and keywords' suggests it suits fuzzy/natural-language queries, and 'optionally on one board' suggests scoping. There is no explicit when-to-use versus filter_tasks/list_tasks, and no statement of 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources