Skip to main content
Glama

Coline

Show a view as…

build_task_view_layout

Asks Kairo to build a layout for a view from a sentence ("a map of who is overloaded", "a burn-up by week"). It is built once in the background and runs on the view's live tasks.

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>",
      "request": "<request>"
    },
    "name": "build_task_view_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewIdYes
requestYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
builtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, openWorldHint=false; the description adds real behavioral context beyond that — the build happens once, in the background, and the resulting layout executes against the view's live tasks. It does not say whether an existing layout is replaced, how long the build takes, or how to observe completion, but the async and live-binding traits are genuinely additive.

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 tight sentences: purpose and concrete example inputs first, then the build/live-data semantics. No filler, and the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need not be explained, and the async build trait is covered. Still missing for a non-idempotent mutation: does a second call replace the previous layout, what happens when the sentence cannot be interpreted, and whether any permissions are required.

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 33% — only workspace is documented ("slug from workspaces.list"). The description partially compensates by characterizing `request` as a natural-language sentence with examples, but `viewId` gets no added meaning and no format guidance appears for the request sentence beyond the samples.

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?

A specific verb+resource combo: build a layout for a task view from a natural-language sentence, reinforced by two concrete examples ("a map of who is overloaded", "a burn-up by week"). It is clearly not create_task_view or update_task_view, but the description never names a sibling to sharpen that distinction explicitly.

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 implied: use this when you have a plain-language description of the visualization you want. There is no explicit when-not guidance, no mention of how this relates to creating or updating a view, and no note on prerequisites (e.g., the view must already exist).

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