Skip to main content
Glama

my_work

Retrieve a person’s ready, in-progress, bouncing, and review-returned tickets, led-project milestones, desk items, and spec questions by crew or project so an orchestrator starts only their work.

Instructions

What belongs to the person whose key this is, across the projects handed to a crew that they can see: ready (their tickets that can start: nothing they wait on is open), in_progress (their tickets a station holds, with the holder and stage), bouncing (those of them that came back from review three or more times: count, ladder 3 or 5 and the last reason), led_projects (projects they lead, with the milestones whose tickets are all delivered: milestones_ready_to_check), desk (the open desk items addressed to them) and spec_questions (the open questions a spec asked them as the owner of a repo, always empty without an enterprise licence: answer each with answer_question). crew names your crew; empty means the crew this session belongs to. The orchestrator of a crew works from this, so it starts only its own person's tickets. project (a name or an id) keeps spec_questions to that project: question numbers restart in each project, so name it when you work on one. Empty lists the questions of every project; a name or id you cannot see is an error 404 ("no project 'x' you can see"), so name it exactly. Needs a key with a person.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
crewNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses defaults (empty crew = session's crew), a 404 failure mode with the exact error text, and a licence-gated behavior (spec_questions always empty without an enterprise licence). It also defines the semantics of bucket contents (ready = nothing they wait on is open; bouncing = 3+ returns with ladder 3 or 5). It does not state read-only-ness or result-size expectations, so not 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.

Conciseness2/5

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

The description is a single sprawling run-on sentence with parenthetical nesting three levels deep; the core purpose competes with bucket glosses that the output schema already covers. It is informative but poorly structured and hard to scan, and the bucket-by-bucket explanation bloats it beyond what selection requires.

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?

Given an output schema exists, the definition is more than complete on return semantics, plus it adds what the schema cannot: licence gating, default crew resolution, and 404 behavior. It omits any mention of permissions beyond 'Needs a key with a person' and says nothing about result size or freshness, which are minor gaps for a dashboard tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must define both parameters, and it does: `crew` names your crew and empty means the session's crew; `project` is a name or id, scopes only spec_questions, empty means all projects, and an out-of-scope name returns 404. It adds the non-obvious constraint that exact naming is required and why (per-project question numbering).

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 states a specific resource and scope: 'What belongs to the person whose key this is, across the projects handed to a crew that they can see,' and enumerates the buckets returned (ready, in_progress, bouncing, led_projects, desk, spec_questions). An agent can tell this is a personal work-dashboard aggregation. It does not explicitly contrast itself with siblings like how_is_project or desk_list, so it stops short of 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 a clear context of use ('The orchestrator of a crew works from this, so it starts only its own person's tickets') and states when the `project` filter should be named ('question numbers restart in each project, so name it when you work on one'). It also routes one follow-up action to answer_question. There is no explicit when-not-to-use or named alternative for non-person-scoped views, keeping it below 5.

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