Skip to main content
Glama

List projects

taskhold_list_projects
Read-only

List projects with their open work, one line each. You rarely need this: every tool takes project as a name. Each line has the name, open counts (working, blocked, todo) and id. With project: that project's notes.

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

Input Schema

NameRequiredDescriptionDefault
projectNoProject name, e.g. the repo folder ("api-server"). Any case, or an id. Unknown names match nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Project name, e.g. the repo folder (\"api-server\"). Any case, or an id. Unknown names match nothing.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered; the description adds real behavioral detail beyond that: one line per project, the exact fields returned, and that supplying project switches the response to that project's notes. It doesn't mention empty results or matching behavior for unknown names, which the schema partially covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences, each load-bearing: purpose first, the discouraging usage note second, output shape third. No filler and no repetition of the title.

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

Completeness5/5

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

For a zero-required-parameter read tool with full schema coverage and clear annotations, nothing an agent needs is missing — it knows what it gets back, when to skip it, and what the optional filter changes. No output schema is needed since the line contents are spelled out.

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 coverage is 100%, so the parameter's name format, case-insensitivity and id support are already documented. The description adds one piece of meaning beyond the schema — that passing project returns that project's notes rather than a filtered list line — which is why this sits at the baseline rather than below it.

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?

"List projects with their open work, one line each" gives a specific verb and resource plus the output granularity, and the field list (name, working/blocked/todo counts, id) makes the result shape unambiguous. It reads clearly as distinct from task-listing siblings such as taskhold_list or taskhold_list_labels, though it never names an alternative outright.

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?

"You rarely need this: every tool takes project as a name" is genuine negative guidance — it tells the agent it usually can skip this tool and pass names directly elsewhere. What's missing is the positive trigger (e.g. "call this first when you don't know the project name"), so the when-to-use case is implied rather than stated.

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