Skip to main content
Glama

task_records

Read-onlyIdempotent

Read a task's runs, artifacts, work, or stages without resending project data. Use offsets to page through large records and follow links to operation_read for full details.

Instructions

Read runs, artifacts, work or stages without repeating the project. Large work records link to operation_read for full details. Follow next_offset when more is true.

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": {
      "task_id": "<task_id>",
      "kind": "<kind>"
    },
    "name": "task_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
limitNo
offsetNo
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 a closed-world scope, so the safety profile is covered. The description adds useful behavior beyond that: records may be truncated and redirect to operation_read, and results are paginated via next_offset. It omits scoping details (how task_id constrains results) and any note on what 'without repeating the project' actually means operationally.

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?

Three short sentences with no padding, which is appropriately sized. However, the phrasing is cryptic rather than compact — "without repeating the project" and "when more is true" require the reader to infer meaning, so brevity comes at the cost of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the critical gap remains the required kind parameter: with 0% schema coverage and no enumeration, the agent has no reliable way to know what string to pass. For a tool with two required parameters and a sibling named operation_read, the definition leaves too much to guesswork.

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 description coverage is 0%, so the description carries the full burden, and it does not meet it. The words "runs, artifacts, work or stages" appear to name the values for the required kind parameter, but it never says so or gives exact literal strings, and limit/offset are never explained. The only parameter-adjacent term, next_offset, is not even an input field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is a generic "Read" and the object is a list of loosely related things ("runs, artifacts, work or stages"), which hints at a record-listing tool but never says plainly what a "task record" is. It does not distinguish this from siblings like task_get, task_list, or operation_read beyond a passing pointer to operation_read. An agent can guess the domain but not the precise scope.

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?

It gives one concrete routing rule: large work records should be followed up via operation_read for full details, and to follow next_offset for further pages. It offers no when-not guidance and no explanation of when to choose this over task_get or task_list, so the alternative-selection guidance is only implied.

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