Skip to main content
Glama

Coline

Read a view's tasks

read_task_view
Read-onlyIdempotent

Lists the tasks in a saved or built-in view (builtin:my-tasks, builtin:assigned-to-crew, builtin:waiting-on, builtin:recently-done), across every board the person can open.

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>",
      "viewId": "<viewId>"
    },
    "name": "read_task_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoWhere the page starts (the last answer's nextOffset).
viewIdYes
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

A3.7/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 fully covered. The description adds one genuinely useful behavioral fact — results span "every board the person can open," i.e. permission-scoped cross-board aggregation — but says nothing about pagination behavior or result limits despite an offset parameter.

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?

A single sentence with the core action front-loaded and the identifier examples tucked into a parenthetical. Nothing is redundant and nothing could be cut without losing information.

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?

An output schema exists, so return values need not be described, and the offset parameter's schema text explains paging. The remaining gap is that the description never states results are paginated or that a nextOffset is returned, which matters for a list tool with a 1,000,000 offset ceiling.

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?

Schema coverage is 67%: workspace and offset are documented in the schema, but viewId has no description there. The description compensates by supplying four concrete builtin view identifiers, which is exactly the semantic help an agent needs to construct a valid viewId. It does not explain the format of a saved (non-builtin) view id, leaving a small gap.

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?

The description gives a specific verb and resource ("Lists the tasks in a saved or built-in view") and enumerates concrete builtin view identifiers, which makes the scope unmistakable. It stops short of naming a sibling such as list_tasks or filter_tasks to contrast against, so differentiation is inferred from the word "view" 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?

Usage is only implied: an agent can infer this is the tool to call when it already has a viewId. There is no explicit statement of when to prefer this over list_tasks, filter_tasks, or search_tasks, and no note on prerequisites such as needing a view to exist first.

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