Skip to main content
Glama

projects_list

Lists projects and sub-folders in the project manager, optionally scoped to a folder path like 'Clients/2026'; uses root by default.

Instructions

List projects and sub-folders in the project manager (folder = path like 'Clients/2026'; root by default).

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

Input Schema

NameRequiredDescriptionDefault
folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; "List" does signal a non-destructive read, and the folder/default detail adds real behavioral context about scope. However it says nothing about recursion depth, result ordering, or response shape (no output schema exists), leaving meaningful gaps for a data-access tool.

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?

One front-loaded sentence with a compact parenthetical for the parameter detail; nothing is redundant and the core action appears first.

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?

For a zero-required-parameter read-only listing tool with no output schema, the description covers what is listed, the scope of the listing, and the path semantics. Only the shape of the returned entries and whether sub-folders are recursive remain unstated.

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 description coverage is 0%, so the description must explain the single parameter, and it does: folder is a path such as 'Clients/2026' and defaults to root. That is exactly the meaning the bare schema (a nullable string with default null) fails to convey.

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 a specific verb and resource ("List projects and sub-folders") and scopes it to "the project manager", which distinguishes it from siblings such as lut_list or fusion_comps. It stops short of explicitly naming a contrasting tool, but the purpose 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?

"root by default" implies you can walk the folder hierarchy and that omitting the parameter browses the top level, which is useful implied guidance. There is no explicit statement of when to use this versus other listing tools, nor any prerequisites or exclusions, so guidance remains implicit.

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