Skip to main content
Glama

list_projects

Retrieve a project tree with open-task counts to monitor active work across projects and spot where tasks remain open.

Instructions

Project tree with open-task counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly does not meet it. It discloses that results include a tree shape and open-task counts, which is useful, but never states that the operation is read-only, how deep the tree goes, whether empty projects appear, or how counts are scoped.

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?

One short phrase with zero filler, and the most distinctive detail (open-task counts) is placed where it will be read. It is efficient, though the fragmentary form means it reads more like a field label than an instruction.

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?

For a parameterless list tool with no output schema, the description is minimally adequate: it reveals the return shape (tree plus counts). However, with no output schema and no annotations to fall back on, the description should have said more about what the returned tree looks like and confirmed read-only behavior.

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 is no parameter meaning to convey and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ('Project tree with open-task counts') rather than a verb+resource statement, so what the tool does must be inferred from the name. It does partially differentiate from siblings by signaling hierarchical project data with aggregated task counts, distinguishing it from list_tasks, but the phrasing is too clipped to be unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus list_tasks (flat task listing) or save_project. Nothing states prerequisites, whether it is a read-only enumeration, or in what scenario an agent should prefer this tool over the alternatives.

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