Skip to main content
Glama

Coline

Say where a task is

set_task_status_line

One short line on where this agent is with a task it holds ("Tests pass; opening the change request"). Shown on the task and its card. Also keeps the claim alive.

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>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>",
      "text": "<text>"
    },
    "name": "set_task_status_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
taskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
savedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive mutation. The description adds that the line is shown on the task and its card, and that calling it keeps the claim alive—behavior not captured by the annotations. It does not cover auth or overwrite semantics, but it adds meaningful context.

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 compact sentences with no filler; the purpose, example, display location, and side effect are front-loaded. Every sentence earns its place.

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?

The tool has an output schema and safety annotations, but with four required parameters and low schema coverage, the description should say more about identifying the task/board and the claim prerequisite. It is adequate on purpose and side effects but incomplete on parameter context and invocation prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, and the description explains only the 'text' parameter through a brief example. The workspace, taskboardId, and taskId parameters remain undocumented in both schema and description, so the description does not compensate for the low coverage.

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 states a specific action: writing a single short status line about the agent's progress on a task, with a concrete example. It clearly distinguishes the output from task creation or completion, though it does not name a sibling alternative.

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 by 'where this agent is with a task it holds' and the example update. It does not say when to prefer this over finish_task or add_task_blocker, nor when not to use it. No explicit exclusions or alternatives are given.

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