Skip to main content
Glama

Coline

Waiting on you

list_waiting_on_me
Read-onlyIdempotent

What waits on the person: crew questions, thread questions, Code sessions waiting for them, and commitments.

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": "list_waiting_on_me"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds value by disclosing what the result set contains (four named categories), which the annotations do not. It says nothing about whether results are paginated, scoped to the caller, or how empty results behave, so it goes only modestly beyond the 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?

A single sentence with zero filler, front-loading the resource definition and then the category enumeration. The phrasing 'What waits on the person' is slightly oblique versus a direct verb like 'List', but nothing is redundant or padded.

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?

The tool is a one-parameter read with an output schema, so return-value explanation is unnecessary, and the annotations cover the safety profile; the description's category list fills the remaining gap about what is aggregated. What is missing is any routing signal against the near-named sibling read_waiting_on, which keeps it from a 5.

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?

With a single parameter at 100% schema description coverage, the schema already explains that workspace is a slug obtained from workspaces.list, including an example. The description adds no additional meaning about the parameter or its defaults. Baseline 3 is appropriate since the schema carries the full burden.

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 names the resource concretely by enumerating the four categories it aggregates: crew questions, thread questions, Code sessions waiting on the user, and commitments. An agent gets a clear picture of the payload shape. It never distinguishes itself from the sibling read_waiting_on or from list_my_tasks, so it falls short of a 5.

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?

Usage is only implied by the resource name and the phrase 'waits on the person' – an agent can infer this is the 'what needs my attention' call. There is no explicit when-to-use guidance, no statement of when not to use it, and no pointer to read_waiting_on as the alternative. No misleading content, just absent guidance.

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