Skip to main content
Glama

List projects

list_projects
Read-only

The projects of the organisation this token or session is bound to (the twin of ankra project list): each project's id, name, slug, whether it is the reserved default and whether it is the current one. Projects are rooms inside an organisation (ADR 0022): clusters, applications, environments, stack profiles, pipelines, AI tickets and incidents belong to exactly one; credentials, registries, vaults, buckets, variables, notification routes and DNS zones may be organisation-wide. Users, roles and billing stay organisation-wide. Read-only; a member with only a project assignment sees only that project.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds a genuine authorization nuance — a member with only a project assignment sees only that project. It stops short of return size, pagination, or error behavior for a caller outside any project.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and returned fields are front-loaded, which is correct. However, the ADR 0022 taxonomy sentence enumerating which resources are project-scoped vs. organisation-wide is a long domain digression that does not change how this zero-param tool is invoked.

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

Completeness5/5

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

With no parameters and no output schema, the description carries the burden of describing the return shape, and it does so field by field, plus the visibility rule that determines what comes back. Nothing needed to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description goes further by explaining the semantic meaning of the returned flags (reserved default vs. current) rather than just listing them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource with scope ('the projects of the organisation this token or session is bound to') and names the exact fields returned (id, name, slug, default flag, current flag). The CLI twin reference (`ankra project list`) and the 'current one' flag make it distinguishable from get_current_project without opening either schema.

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?

Gives clear context for when this applies (org-bound session, visibility scoped to project assignment) and notes it is read-only. It does not explicitly route to alternatives such as get_current_project for a single project, so no explicit when-not guidance.

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.