Skip to main content
Glama

task_search

Read-only

Search tasks in a project (lightweight summaries). Always pass projectId. Every successful response includes delegation (your human supervisor, advisory responsibility role, and credential-authorized capabilities) plus projectPolicy; follow both. Responsibility roles never filter results. For multi-workspace OAuth connections, pass workspaceId from statelode://workspace to target a non-default workspace; ungranted ids are rejected. Never guess a projectId: searching never creates anything, and an unknown projectId returns an unknown_project error listing the selected workspace's real slugs (knownProjects) — pick one of those and retry. Every response also includes workflow: this project's statuses as { key, name, category, hidden } — projects define their own columns, so use a key (stable) or a category for status, never a display name. With NO status, results are limited to 'active' tasks only — so an empty result does NOT prove a task is absent; pass an explicit status (or an array, e.g. backlog+active+in_progress+review+done+blocked) before concluding nothing matches. Default limit is 10 (max 50). The response echoes appliedStatus and appliedLimit, and sets hasMore:true when the limit truncated the results. Optional sprint filter: a sprint id, 'active' (the project's active sprint), or 'none' (unsprinted). Use this FIRST; only call task_get when you need a full body.

Input Schema

NameRequiredDescriptionDefault
limitNo
ownerNo
queryNo
sprintNo
statusNo
workerNo
assigneeNo
priorityNo
requestsNo
projectIdYes
workspaceIdNoA workspace id from statelode://workspace. Explicit input overrides every default. For repository work, pass the workspaceId pinned in statelode.json. Project-creating mutations require this when a multi-workspace grant has no human-selected default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description details behavioral traits far beyond the minimal annotations, including response structure (e.g., 'delegation', 'projectPolicy'), error handling logic (unknown_project error), and multi-workspace OAuth requirements.

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?

The description is dense, but every sentence is highly intentional, addressing a specific operational or behavioral requirement. It is logically structured to guide complex tool usage.

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 high operational complexity, involving multi-workspace contexts, defined project policies, and explicit filtering rules, this description is exceptionally complete.

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?

Given the extremely low schema coverage (9%), the description provides crucial context for complex parameters like 'projectId' (error handling if missing) and 'status' (how it affects result scope), effectively compensating for the missing schema detail.

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 clearly defines the purpose as a 'lightweight' search for tasks, setting it apart from the full body retrieval of task_get and the mutation function of task_mutate.

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 explicit hierarchy instructions ('Use this FIRST'), detailed rules for filtering (e.g., 'NO status' = 'active' only), and necessary operational constraints (e.g., 'Always pass projectId').

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.