Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

Finds projects accessible to the connected account and its workspaces, optionally filtered by name or workspace. Omitted workspace selection includes all accessible spaces; null selects Personal.

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
searchNo
workspace_idNoOmit to list all accessible projects. Pass null for Personal only, or an exact workspace ID to filter. Applies to this request only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful scope context by stating which projects are visible and how workspace omission versus null changes the result set. It does not describe pagination or return ordering, but it adds meaningful behavior beyond the annotations.

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?

Two tightly written sentences, front-loaded with the tool's scope and followed by the workspace-selection nuance. There is no redundant or filler wording.

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 simple list tool with only two optional parameters and no output schema, the description covers visibility scope and filter semantics adequately. The main remaining gap is that it does not mention pagination or result ordering, which an agent might otherwise need.

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 50%: workspace_id is well documented in the schema, while the generic search parameter has no schema description. The description compensates by clarifying that filtering can be by name or workspace and by restating the omitted/null workspace semantics.

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 uses a specific verb and resource: it finds projects accessible to the connected account and its workspaces, optionally filtered by name or workspace. This clearly distinguishes list-style project discovery from single-project access, though it does not explicitly name the get_project sibling.

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?

It explains how the optional name and workspace filters work, including that omitted workspace selection includes all accessible spaces and null selects Personal. It does not state when to use this instead of get_project or list_workspaces, so usage guidance is implied rather than explicit.

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