Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

List the projects accessible to the calling principal. Returns id, slug, name, status, createdAt for each. An empty list means the workspace is not set up yet: no mission can run until the person connects GitHub and a model key and creates a project in the SHIP console. Call get_setup_progress and give the person the console page of its next step.

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
limitNoMax results (default 20)
cursorNoOpaque pagination cursor from a previous call

Output Schema

NameRequiredDescriptionDefault
dataYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / data / items / properties / provisionedBy
      Added value: +{
      +  "enum": [
      +    "ship",
      +    "owner"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / items / properties / siteTemplate
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / data / items / required
      Previous value: -[
      -  "id",
      -  "orgId",
      -  "slug",
      -  "name",
      -  "status",
      -  "tracker",
      -  "trackerConnectorId",
      -  "trackerTeamId",
      -  "trackerProjectId",
      -  "scmConnectorId",
      -  "scmOwner",
      -  "scmRepo",
      -  "llmConnectorId",
      -  "autoMerge",
      -  "issueCode",
      -  "defaultSandboxTemplateId",
      -  "createdAt"
      -]New value: +[
      +  "id",
      +  "orgId",
      +  "slug",
      +  "name",
      +  "status",
      +  "tracker",
      +  "trackerConnectorId",
      +  "trackerTeamId",
      +  "trackerProjectId",
      +  "scmConnectorId",
      +  "scmOwner",
      +  "scmRepo",
      +  "llmConnectorId",
      +  "autoMerge",
      +  "issueCode",
      +  "defaultSandboxTemplateId",
      +  "siteTemplate",
      +  "createdAt"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / tracker / enum
      Previous value: -[
      -  "linear",
      -  "github-issues",
      -  "none"
      -]New value: +[
      +  "linear",
      +  "github-issues",
      +  "jira",
      +  "none"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the non-obvious behavioral fact that an empty result is a meaningful state (workspace not set up) rather than a failure or a filtering artifact, which is real value 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.

Conciseness4/5

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

Front-loaded with purpose, then return shape, then the empty-state branch and next action. The field enumeration (id, slug, name, status, createdAt) is partly redundant given an output schema, but the sentences otherwise earn their place.

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?

An output schema exists, so the return-value explanation is redundant but harmless, and the empty-state semantics plus the follow-up tool call are exactly the context an agent needs to act correctly. Only pagination/limit behavior is left entirely to the schema, which is adequate for a simple read.

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 description coverage is 100% with only limit and cursor, both already documented in the schema. The description adds nothing about pagination or result limits, so baseline 3 applies.

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 and resource with scope: 'List the projects accessible to the calling principal.' That scope clause distinguishes it from other list_* siblings that cover different resources, and an agent can tell immediately what it returns.

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 a concrete escalation rule: when the list is empty, call get_setup_progress and surface the console page of its next step. It does not spell out when *not* to call this tool or how it relates to other list_* tools, but the onboarding branch is unusually actionable 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.