Skip to main content
Glama

Coline

Read what you're waiting on

read_waiting_on
Read-onlyIdempotent

Everything other people owe you, grouped by who: tasks you made or own that someone else has or that wait on someone, your tasks blocked by someone else's task, tasks handed outside, work given to crew or your agents, and promises made to you in mail and chat with no task. Optionally for one project.

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": {
      "workspace": "<workspace>"
    },
    "name": "read_waiting_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
totalYes
groupsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit beyond that by disclosing the aggregation behavior ("grouped by who") and by drawing non-obvious inclusion boundaries, notably that mail/chat promises count only when there is no backing task. It says nothing about ordering, pagination, or size of the result set.

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?

A single sentence, front-loaded with the core purpose and then a comma-delimited enumeration of the coverage categories, which is an efficient structure for a scoping-heavy read tool. It is dense and the trailing "Optionally for one project" is tacked on rather than integrated, but no sentence is wasted.

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?

With only two parameters, one undocumented in the schema (compensated in prose) and an output schema present to carry return structure, the description supplies enough to call the tool correctly and to anticipate the grouping shape. The remaining gap is disambiguation from the similarly named inverse tool, which the definition does not address.

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

Parameters4/5

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

Schema coverage is 50%: workspace is documented inline (slug from workspaces.list) while projectId has no schema description at all. The description compensates for that gap with "Optionally for one project," which conveys both that projectId is optional and that it narrows the scope to a single project. No format or edge-case detail beyond that, but the meaning is clear.

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 opens with a specific verb-and-resource framing ("Everything other people owe you") and then enumerates the exact categories included — owned tasks held by others, tasks blocked by another task, work handed outside, work delegated to crew/agents, and untasked promises from mail and chat. That is a substantive, distinguish-ish scope statement, but it never names the near-identical sibling list_waiting_on_me, so the agent must infer the direction of the relationship from the name alone.

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?

Use is implied rather than directed: the enumeration of what counts as "waiting on" implicitly tells the agent when this tool applies, and "Optionally for one project" signals the scoped variant. There is no explicit when-not guidance and no pointer to the inverse sibling, so an agent choosing between this and list_waiting_on_me gets no help.

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