Skip to main content
Glama

desk_list

Lists open, answered, or withdrawn questions across projects, prioritizing blockers and oldest items, with filters for project and questions assigned to you.

Instructions

The desk: open questions (or answered, withdrawn) across every project, blockers first, then oldest. mine keeps the ones addressed to the person whose key this is. Ask the first one.

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

Input Schema

NameRequiredDescriptionDefault
mineNo
stateNoopen
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose behavior beyond the schema: default sort order (blockers first, then oldest), cross-project scope by default, the accepted state values, and the identity semantics of `mine`. It does not mention result limits, pagination, or permissions, but the shape of the read is well conveyed.

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?

Roughly forty words, no filler, with scope and ordering front-loaded and the usage hint last. The telegraphic backtick style and the elliptical 'Ask the first one' border on under-specification, but nothing is redundant.

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

Completeness3/5

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

An output schema exists, so return shape need not be explained, and the core listing behavior is covered. The gaps are the undocumented `project` filter and the absence of any hint on how this list connects to the sibling action tools, which matters for a read tool whose purpose is to feed desk_answer or desk_withdraw.

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 0%, so the description must compensate, and it does for two of three parameters: `mine` is defined as 'ones addressed to the person whose key this is' and `state` gains the allowed values `open`/`answered`/`withdrawn`. The `project` parameter is never addressed — 'across every project' describes the default but does not explain what passing a project does.

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 a specific resource (open questions on the desk), its scope (across every project), and the state variants it can return (`answered`, `withdrawn`). The verb is implicit in the noun-phrase framing 'The desk: open questions' rather than stated as 'List', but the retrieval action and the add/answer/withdraw siblings are still distinguishable.

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?

'Ask the first one.' gives a workflow cue — list first, then engage the top question — and the ordering note (blockers first, then oldest) reinforces that. There is no explicit when-not guidance or reference to desk_answer/desk_withdraw for acting on a question, so the agent must infer the handoff.

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