Skip to main content
Glama

Coline

Read a task

get_task
Read-onlyIdempotent

Reads one task with its full description, assignees, status and fields.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id from list_tasks, find_task or get_task.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/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 without the description. The sentence adds a useful note that the full description and assignees are included in the payload, but says nothing about failures (unknown taskId), scope, or payload size.

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 zero filler; the returned fields are listed rather than padded with prose. It is efficient, though it spends its only clause on output content that the output schema already covers.

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?

For a simple single-record read, the description plus full schema coverage, complete annotations and an output schema leave little an agent needs to know before calling it. Only error behavior and payload-size expectations are unaddressed.

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 100% and each of the three required ids is documented with its source tool in the schema. The description adds no additional meaning about taskId, taskboardId or workspace, so the baseline of 3 applies.

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 ("Reads one task") and enumerates what comes back (full description, assignees, status, fields). It is clear enough to distinguish from read_task_history, read_task_state and find_task by implication, but the description never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. The agent must infer from the name that this is for fetching a single known task id and that find_task handles searching and read_task_history handles the audit trail; the description says none of this.

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