Skip to main content
Glama

Coline

Filter tasks across boards

filter_tasks
Read-onlyIdempotent

Runs filters, grouping and sorting over tasks without saving a view: on some boards, all boards, a project or a cycle.

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>",
      "scope": "<scope>",
      "query": "<query>"
    },
    "name": "filter_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
scopeYes
offsetNoWhere the page starts (the last answer's nextOffset).
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
tasksYes
totalYes
stillSortingYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes one real behavioral fact — results are not persisted as a view — but says nothing about result limits, pagination behavior, or what the grouped/sorted response looks like.

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 front-loaded sentence with no filler, though the clause "on some boards, all boards, a project or a cycle" is slightly awkward and could map more cleanly to the scope union values.

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?

For a tool with a three-level nested query object, required scope union, and pagination, the description is thin — an output schema exists so return values need not be explained, but the description does not convey query breadth (filters, groupBy, pill, sort) in a way that helps an agent compose a valid call.

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 50%, with prose descriptions only on workspace and offset. The description's list of scope kinds mirrors the scope oneOf union and mentions grouping/sorting/filters at a high level, but adds no format or constraint detail for the deeply nested query object.

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: runs filters/grouping/sorting over tasks, and clarifies the scope options (boards, all boards, project, cycle). The phrase "without saving a view" separates it from saved-view reads, though it never names a sibling tool directly.

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?

"Without saving a view" implies a transient/ad-hoc query use case, which is useful positioning, but there is no explicit guidance on when to pick this over list_tasks, search_tasks, or list_my_tasks, and no prerequisites are stated.

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