Skip to main content
Glama

Read delegated work on a todo

well_get_delegated_work
Read-onlyIdempotent

Read the work Well did on a todo the person handed to Well: the newest run's one-line summary, the work it drafted or found, and the one question it asks the person.

Call it when the person asks what Well did or asked on a todo that waits on them, or before you act on a yes for that todo. Pass the todo's id from the waiting list in the turn context.

Only the member the run answers to reads the work. For anyone else, or for a todo with no delegated work, the answer is that nothing was found.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe id of the todo, from the waiting list or the task.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
workNoWhat Well drafted or found on the todo. It is Well's text, never the person's ask.
errorNo
statusNoThe state of the newest run: needs_you, done, failed, skipped or cancelled.
successYes
summaryNoThe one-line summary Well wrote for the report.
questionNoThe one thing Well asks the person. An empty string when Well asks nothing.
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds genuinely new behavior — an authorization rule (only the member the run answers to may read) and a defined empty result ('nothing was found') for unauthorized or work-free todos. It does not describe recency semantics of 'newest run' or whether older runs are visible, which keeps it just short of the top.

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?

Front-loaded with the core purpose and what is returned, then usage triggers, then authorization, then workspace handling — a sensible ordering. The final paragraph restates the workspace_id requirement already present in the schema, so it is slightly redundant but not padded.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to explain shapes, and it still covers the two things structured fields cannot: who is allowed to see the result and what an empty/denied lookup looks like. Nothing an agent needs in order to call this correctly is missing.

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%, so all four parameters are already documented, including the workspace_id conditional and the conversation_id threading rule. The description reinforces the workspace_id behavior and task_id provenance but adds little syntax or edge-case meaning the schema does not already carry — the baseline 3 for high coverage applies.

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

Purpose5/5

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

The first sentence names a specific verb (read) and resource (the work Well did on a delegated todo) and enumerates exactly what comes back: the newest run's one-line summary, the drafted or found work, and the single question asked. That is narrow enough that an agent can distinguish it from generic task readers like well_get_task or well_get_worklist_status.

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

Usage Guidelines5/5

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

It gives two concrete triggers ('when the person asks what Well did or asked' and 'before you act on a yes for that todo') and states where the task_id comes from (the waiting list in turn context). It also adds workspace-call routing: call directly for a single-workspace token, pass workspace_id when several are authorized.

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