Skip to main content
Glama

what_needs_me

Shows what is waiting for you right now, oldest first, with each item's project and wait time so you can see what to do next or what is stuck.

Instructions

What is waiting for the person right now: the same list the home page shows under "Waiting for you", oldest first with the projects ready to close last, each with what it is, which project it belongs to and how long it has waited. Start here when the person asks what to do next or what is stuck.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 burden and does so reasonably: it discloses ordering (oldest first, projects ready to close last) and per-item payload (identity, project, wait time), which tells the agent this is a read-only, already-prioritized list. It does not explicitly state side effects (none expected) or limits on list size, leaving a small gap.

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?

Two sentences, front-loaded with what the list is, then the cue for when to call it. The embedded ordering clause is a bit comma-heavy and the line break inside the sentence is an artifact, but no wording is redundant.

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?

An output schema exists, so return values needn't be specified, and the description still outlines item shape and sort order. For a zero-parameter, query-only tool this is nearly complete; only the absence of any statement about result volume or whether the list can be empty is missing.

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?

The tool takes zero parameters, so there are no parameter semantics to add; baseline 4 applies. The description correctly avoids inventing filter arguments that the schema does not support.

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?

States a specific resource precisely: the list of items waiting on the person, explicitly equated to the home page 'Waiting for you' panel, with item content (what it is, project, wait duration). It implicitly separates itself from what_happened ('what happened') and what_is_broken ('what is stuck'), though it never names a sibling directly.

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?

'Start here when the person asks what to do next or what is stuck' gives a clear entry-point condition for invocation. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is strong context rather than full routing guidance.

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