Skip to main content
Glama

tasks_get

Read-onlyIdempotent

Read current task state by default, bounded to about 12,000 JSON characters, with history counts and expansion instructions. view=relationships pages explicit links and parent/replacement-field links, current target state and supersession pointers; task_id leads to the target. Missing targets and partial pointers are explicit. view=history pages comments, activity, guidance revisions or review records (kind), newest first with stable ID ties; default 5. view=field expands an omitted top-level field as bounded JSON-text chunks; a history field also takes kind and event_id. The same read options with next_cursor as cursor continue. History uses a keyset and initial rowid/time upper bounds; appends do not restart it, deletions disappear, and edited bodies are live. Membership is not frozen: deletion followed by a same-timestamp insert can admit a new event on a later page. Field chunks reject changed content with CURSOR_STALE; a new field read returns the current content. view=full explicitly requests the unbounded compatibility response with all comments/activity ordered oldest first (created_at ASC, id ASC). Prefix task IDs work when unique.

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": {
      "project_id": "<project_id>",
      "task_id": "<task_id>"
    },
    "name": "tasks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoHistory kind; defaults to comments. revisions holds saved guidance text; reviews holds explicit account review records.
viewNoTask view; current by default. relationships pages linked task references and replacement pointers without comments or document bodies. full is explicitly unbounded.
fieldNoTop-level field to expand with view=field.
limitNoHistory or relationship rows per page (default 5, cap 20); response budget can return fewer.
cursorNoOpaque next_cursor from the previous page, valid only with the original filters and view. It cannot be combined with offset.
offsetNoFresh row offset, or UTF-16 character offset for field expansion. Cursor provides checked continuation when available.
task_idYesTask ID (starts with tsk_). Prefixes are accepted when unique inside the project.
event_idNoHistory event ID for a field expansion; kind is repeated.
project_idYesProject ID (UUID), subdomain, or slug, resolved server-side; 'default' is the organization's shared task board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description adds substantial behavior beyond that: a ~12,000 character response budget, keyset pagination semantics, that appends do not restart history and deletions disappear, that edited bodies are live, and that same-timestamp insert-after-delete can admit a new event on a later page. It also discloses CURSOR_STALE on field chunk expansion and that a fresh field read returns current content — exactly the kind of non-obvious behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the default read and contains almost no filler, so the content earns its place. However, the prose is a dense semicolon-chained run of clauses where several sentences carry two or three separate ideas, which makes it hard to scan for the one behavior an agent needs at call time.

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 9-parameter read tool with no output schema, the description covers defaults, paging, ordering (created_at ASC, id ASC for full), cursor lifecycle, and staleness errors well. It does not describe the general response envelope or other error codes, which is a modest gap given there is no output schema to fall back on.

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 100%, so the baseline would be 3, but the description earns more by explaining interactions the schema can only hint at: that kind and event_id combine for history field expansion, that task_id prefixes resolve when unique, and how next_cursor as cursor continues with the same read options. It still leaves the field+cursor+offset interaction somewhat implicit.

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 opens with a specific verb+resource+default: 'Read current task state by default, bounded to about 12,000 JSON characters'. It then enumerates the distinct view modes (current/relationships/history/field/full), so an agent understands exactly what class of read this is. It never names a sibling tool (tasks_list, tasks_overview) to contrast against, so it stops short of a 5.

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

Usage Guidelines4/5

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

It gives clear selection guidance among the tool's own modes: default current, view=relationships for links only, view=history for comments/activity/revisions/reviews, view=field for expanding an omitted field, and view=full as an explicit unbounded opt-in. What's missing is any routing advice versus other tools such as tasks_list or tasks_overview, so the agent must infer that boundary.

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