Skip to main content
Glama

list_projects

Read-onlyIdempotent

Retrieve workspace projects with their IDs, names, and slugs to find the project_id required by other tools; archived projects stay hidden unless include_archived is true.

Instructions

List the projects in the workspace with their ids, names and slugs. Call it first to find the project_id that most other tools require. Archived projects are hidden unless include_archived=true.

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
workspace_idNoWorkspace UUID. Defaults to the calling agent's workspace; another workspace is only readable if your key belongs to it.
include_archivedNoAlso list archived projects. Default false: only active projects are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.6
    • changedInput schema / properties / include_archived / description
      Previous value: -"Include archived projects."New value: +"Also list archived projects. Default false: only active projects are returned."
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Workspace ID. Defaults to agent's workspace."New value: +"Workspace UUID. Defaults to the calling agent's workspace; another workspace is only readable if your key belongs to it."
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact not present in the annotations: archived projects are silently filtered out unless include_archived=true, which is exactly the kind of default-result skew an agent could misread.

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: what it returns, when to call it, and a default-behavior caveat. The most actionable guidance (call it first) is front and center and nothing is padded.

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?

With no output schema, the description usefully enumerates the returned fields and covers the archived-filtering default, which is enough for an agent to call it correctly. It leaves result volume and ordering unpinned, a minor gap for a two-parameter listing tool.

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% and both parameters are fully described in the schema, including the defaults and the workspace-access caveat. The description's mention of include_archived restates the schema's default rather than adding syntax, format, or interaction detail, so the baseline of 3 applies.

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?

States a specific verb and resource and names the payload the caller gets back ('ids, names and slugs'), which is more than a restatement of the name. It implicitly separates itself from the single-project sibling (get_project) by framing itself as the enumeration step, but never names that sibling explicitly.

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?

"Call it first to find the project_id that most other tools require" gives a concrete ordering rule that tells the agent when to reach for this tool before others. It stops short of an exclusion rule (e.g., skip this and call get_project when you already have a slug or name).

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