Skip to main content
Glama

task_getById

Retrieve a single user task by ID to view its name, assignee, due date, priority, and process instance. Use it to inspect task details before acting on a workflow.

Instructions

Retrieve a single user task by its ID. Returns task name, assignee, due date, priority, and process instance.

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": {
      "id": "<id>"
    },
    "name": "task_getById"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only lookup and names the returned fields, but says nothing about authorization requirements, whether historical/completed tasks are retrievable, or how a missing ID is surfaced. For an unannotated tool, that leaves meaningful behavioral gaps.

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?

Two short sentences with no filler, and the core action leads. The second sentence earns its place because there is no output schema to document the response. It could still be tightened by folding the return-field list into a more compact clause.

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?

For a one-parameter lookup with no annotations and no output schema, the description does the minimum viable job: it names the action, the key, and the returned fields. It omits ID format and failure behavior, which an agent needs to call it correctly the first time, so it is adequate rather than complete.

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?

The single id parameter has 0% schema description coverage, so the description must compensate. It only restates 'by its ID' without giving the identifier's format (numeric vs UUID), its source, or any constraint, adding essentially no meaning beyond the bare schema property.

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 verb and resource: 'Retrieve a single user task by its ID.' The 'user task' scoping plus the singular 'single' distinguishes it from bulk siblings like task_list, and the task_ prefix separates it from deployment_getById or incident_getById. It stops short of any explicit sibling comparison, so it is clear but not fully differentiated.

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: 'by its ID' signals the precondition that the caller must already hold a task identifier, which naturally excludes search-style workflows. There is no explicit statement of when to pick this over task_list or task_getVariables, and no mention of what happens if the ID is unknown or refers to a completed task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools