Skip to main content
Glama

Coline

List task views

list_task_views
Read-onlyIdempotent

Lists the task views the person can open: their own, the team's, and the built-in ones (My tasks, Assigned to crew, Waiting on, Recently done). Optionally only views saved on one board, project or 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>"
    },
    "name": "list_task_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeIdNo
homeKindNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
viewsYes
builtInYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context not in the annotations: which visibility tiers of views are returned and that the board/project/cycle filter narrows that set. It omits pagination and result-size behavior, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the what-it-returns information front-loaded and the optional narrowing stated second. The parenthetical built-in view names are worth their space because they tell the agent what to expect in results.

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

Completeness4/5

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

With an output schema present the description need not explain return values, and annotations cover safety, so the remaining burden is scope and filtering — both addressed. The gaps are modest but real: the homeId/homeKind pairing rule and any pagination or ordering behavior are unaddressed for a 3-parameter filtered list 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 coverage is only 33% (only the workspace slug is described in the schema), so the description must carry the two undocumented filter parameters. It does partially: "views saved on one board, project or cycle" maps directly onto homeKind's board/project/cycle enum and conveys that homeId scopes to one container. It never states that homeId and homeKind are a pair that must be supplied together, nor what happens if only one is given, so the baseline 3 is appropriate.

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 ("Lists the task views") and enumerates the exact scope returned: own, team's, and the built-in views (My tasks, Assigned to crew, Waiting on, Recently done). This clearly separates it from single-view readers like read_task_view, though it never names that sibling explicitly, so routing is inferred rather than stated.

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?

"Optionally only views saved on one board, project or cycle" implies when the filter should be applied, and the word "Optionally" signals the unfiltered call is the default. However, there is no explicit guidance on when to pick this over read_task_view or build_task_view_layout, and no stated preconditions.

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