Skip to main content
Glama

list_projects

Read-onlyIdempotent

List workspace projects with boards, admins, chat IDs, and task counts, including hidden archived projects when requested. Use returned project IDs or titles in other project arguments.

Instructions

Projects in the workspace with boards, admins, chat id and (by default) task counts: total / done / open / overdue / mine_open.

Archived projects are hidden unless include_archived=True. project arguments elsewhere accept these ids or titles.

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
with_countsNo
include_archivedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuine non-schema behavior: archived projects are hidden by default, counts are computed by default, and the returned ids are reusable as `project` arguments elsewhere. It says nothing about cost of count computation or result size/pagination.

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 tight paragraphs with zero padding, and the core content (what is returned) is front-loaded ahead of the default/flag behavior. The fragment style ('Projects in the workspace with...') is slightly clipped and 'mine_open' is left unexplained, but nothing is wasted.

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 output schema covers return structure and rich annotations cover safety, so the description only needs defaults and cross-tool semantics, both of which it supplies. The remaining gap is scale behavior: no indication of result volume or whether computing counts is expensive enough to warrant with_counts=false.

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?

With 0% schema coverage, the booleans carry no documentation in the schema, yet the description explains the effect and default of both: counts are included 'by default' (the with_counts toggle) and archived projects stay hidden 'unless include_archived=True'. It does not name the parameters literally, but the semantics are recoverable.

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 (workspace projects) and enumerates the returned fields (boards, admins, chat id, task counts), which clearly separates it from singular siblings like get_project or get_projects_summary. It never uses an explicit verb like 'list', relying on the name plus field enumeration, but the intent is unambiguous.

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 context is implied rather than stated: the archived-visibility rule and the note that other tools accept these ids/titles tell the agent where the output is useful downstream. There is no explicit 'when to use this vs get_project / get_task_counts' guidance, leaving the agent to infer selection among sibling tools.

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