Skip to main content
Glama

List projects

list_projects
Read-only

Projects in the caller's organization. Every asset and job belongs to one; when a tool's project is omitted the API key's default project (or the organization's default) is used. project accepts a project id or slug. Set archived=true to include archived projects alongside active ones.

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
archivedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: default-project resolution for other tools and the active/archived filtering behavior. It omits ordering, pagination, and whether all org projects are returned regardless of key scope.

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?

Four short sentences, none wasted; the org scope is stated first, followed by the project-resolution rule and the one parameter's effect. The middle sentences about `project` are background that supports sibling calls rather than this tool, which softens the front-loading slightly.

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 an output schema present and only one optional boolean parameter, the description needn't explain return values, and it covers scope, filtering, and default-project semantics. Remaining gaps (ordering, pagination, empty-list behavior) are minor for a simple list tool.

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 0% and the single parameter has only a default value in the schema, so the description must compensate – and it does: "Set archived=true to include archived projects alongside active ones" explains the default exclusion and what true yields. The discussion of `project` accepting an id or slug is cross-tool context rather than a parameter of this tool, which slightly blurs the mapping.

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 identifies the resource and its scope: "Projects in the caller's organization," which pairs with the name to make clear this enumerates projects. It does not use an explicit verb or contrast itself with siblings such as create_project or list_assets, but the scope statement is specific enough for an agent to distinguish it.

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 provides useful indirect guidance by explaining that every asset and job belongs to a project and that an omitted `project` falls back to a default, implying this tool is how you discover projects. It never states explicitly when to call this versus create_project or update_project, nor does it say to call it before other tools to obtain a project id.

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