Skip to main content
Glama

list_projects

Retrieve available projects with their IDs, names, templates, and statuses, or resolve a single project by its key.

Instructions

List the projects you can work in: id, name, template and status. With a project key it is the one project the key belongs to.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the shape of the returned records, which is genuinely useful, but says nothing about permissions, ordering, volume, or whether results are limited to the caller's membership beyond the phrase "you can work in".

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 sentences with the primary action front-loaded and the returned fields enumerated immediately after. Only the unexplained "project key" clause adds ambiguity rather than length problems.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and an output schema exists, so return values need not be explained in depth. However, the reference to a project-key input that the schema lacks leaves the calling contract inconsistent, which is a meaningful gap for a zero-parameter 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?

The schema declares zero parameters, so the baseline would be 4, but the description references "a project key" that does not exist in the input schema. That mismatch introduces a phantom parameter and could lead an agent to attempt a call shape the tool does not accept.

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 gives a specific verb and resource ("List the projects") and scopes it to "projects you can work in", then names the returned fields (id, name, template, status). It does not distinguish itself from sibling list tools such as crew_projects or catalog_list, but the resource 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 is only implied: the second sentence hints at a lookup mode, but it never states when to use this tool versus the many sibling list_* and *_projects tools, nor any prerequisites. An agent can infer the basic context but gets no explicit routing guidance.

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