Skip to main content
Glama

Read more of a work item

read_work
Read-onlyIdempotent

Retrieve one page of a long work item, or the full item with instructions, tools, and conversation, when you need to recover context before responding.

Instructions

Read one page of a long work item, or (full: true) get the item again in full: its instructions, every tool and the whole conversation, for when you lost track of it. When a work item says it has several pages, read all of them before you respond.

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": {
      "work_id": "<work_id>"
    },
    "name": "read_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoSend the whole item again instead of one page (after your context was compacted, or when you no longer have the instructions or tools it refers to).
pageNoThe page to read, from 2.
work_idYesThe workId of the work item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds the useful behavioral detail that full mode re-sends the entire item (instructions, all tools, whole conversation) rather than a single page, and that multi-page items must be fully read before responding. It does not describe return shape or page-size limits, so it adds moderate value beyond annotations.

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?

Only two sentences, with the primary behavior and the alternative mode front-loaded, followed by a short directive about multiple pages. Slightly dense phrasing in the first sentence but no wasted text.

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 simple three-parameter read tool with no output schema, the description covers the key modes and the multi-page workflow. However, it leaves gaps around what a single page contains, how many pages typically exist, or what work_id format looks like beyond the schema wording, so completeness is adequate rather than thorough.

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 coverage is 100% and each parameter is already documented, including page starting from 2 and the full reload semantics. The description's meaning for full: true largely mirrors the schema's own wording, adding only the workflow cue about context compaction and completing all pages. Baseline 3 is appropriate when the schema carries the parameter detail.

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 concrete verb and resource: reading a page of a long work item, plus the alternate mode (full: true) that reloads the whole item with instructions, tools, and conversation. This is clearly distinguishable from passage/lesson readers by its 'work item' scope. It stops short of explicitly naming a sibling tool for comparison, so it is strong but not maximal.

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?

Gives clear conditions for both modes: use one page normally, use full: true when you lost track of the item or your context was compacted, and read every page before responding when the item reports multiple pages. It does not state when to avoid this tool or point to a specific alternative, which keeps it below a 5.

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