Skip to main content
Glama

List projects

list_projects
Read-only

List the projects visible to this token (a project-scoped token sees only its project). A project with a 'parent' is a subproject of that one: it has its own issues, board and wiki, and shares only who may reach it. Archived projects — finished work put away, read-only — are left out unless includeArchived is true; 'archivedLeftOut' then counts them.

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
includeArchivedNotrue to list archived projects too, each marked 'archived: true'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeArchived
      Added value: +{
      +  "default": false,
      +  "description": "true to list archived projects too, each marked 'archived: true'.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/openWorld, so the safety profile is covered. The description adds meaningful behavior beyond that: visibility is token-scoped, subprojects share only reachability with their parent, archived projects are read-only and omitted by default, and an 'archivedLeftOut' count is returned — return-shape detail that matters given there is no output schema.

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?

Front-loaded with scope, then subproject semantics, then the archived default — a logical order. The parenthetical and em-dash asides are dense but each carries real information; only the subproject sentence is arguably more than a list call strictly needs.

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?

One optional parameter and no output schema make this a simple tool, and the description covers scope, default filtering, and two return fields (archived flag, archivedLeftOut). Pagination or ordering isn't mentioned, but nothing suggests large result sets requiring it.

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?

Schema coverage is 100% for the lone parameter, so the baseline is 3. The description goes beyond the schema by explaining the consequence of the flag (archived projects appear and are counted via archivedLeftOut), not just its type.

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

Purpose5/5

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

States a specific verb and resource ('List the projects') plus the exact scope ('visible to this token'), which distinguishes it from create_project, archive_project, and the many other project-scoped siblings. The subproject and archive sentences further pin down what 'project' means here.

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?

Gives clear usage conditions: it enumerates everything the caller's token can see, and archived projects are excluded unless includeArchived is true. It doesn't name a sibling alternative (e.g., list_project_presets or list_project_fields) for related needs, but for a simple list tool the when-to-use guidance is essentially complete.

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