Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Work list

work_list
Read-only

Lists the plan's work: every task on the calendar of one plan revision, each with its id, key, kind, engine, who does it (executor), title, channel, day, state, forecast (expected), the number that verifies it, what it is linked to (refs) and when it last changed. Use it to see what is planned or where a piece stands; work_get opens one row whole with its history and numbers, and the later days still held as slots are in situation_read. Every row of the revision, never a page of them.

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": {
      "state": "<state>",
      "revision": "<revision>"
    },
    "name": "work_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesWhich rows: scheduled (waits for its day to reach the week ahead), planned (in the week, not started), accepted (its engine took it), in_progress (being made), awaiting_owner (a card waits for the owner), published (went out), done (finished), dropped, failed or cancelled; all for every state.
projectNoThe project's id or exact name. Optional when the account has one project.
revisionYesThe plan revision to read, as journal_read lists them; null for the current plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the description doesn't need to re-litigate safety. It adds real value beyond that: a full inventory of returned fields (id, key, kind, engine, executor, title, channel, day, state, forecast, verifying number, refs, last changed) and the guarantee 'Every row of the revision, never a page of them', which rules out pagination concerns. It stops short of noting permissions or ordering, so not quite a 5.

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?

Three sentences, front-loaded with the scope statement before the routing guidance. The long field enumeration in sentence one is dense but earns its place because no output schema exists. Slight redundancy in 'lists the plan's work' and 'Every row ... never a page of them'.

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?

There is no output schema, and the description compensates by enumerating what each row contains. Combined with the no-pagination guarantee and explicit sibling routing, an agent has everything needed to decide and call correctly.

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% and the state enum values are individually explained in the schema, so the description carries little additional parameter burden. It does confirm that 'revision' means the same revision journal_read lists ('as journal_read lists them' is in schema), but the description itself adds no filtering syntax or default behavior. Baseline 3 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?

States a specific verb and resource — 'Lists the plan's work: every task on the calendar of one plan revision' — with the row scope spelled out. It clearly separates itself from work_get (one row) and situation_read (later-day slots) without the agent needing to open any schema.

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?

'Use it to see what is planned or where a piece stands' gives the selection condition, then names two alternatives with their distinct purposes. Both the when-to-use and the when-to-use-something-else are explicit.

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

All Marsell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources