Phare

List projects

list_projects

Read-onlyIdempotent

Get a paginated list of the projects you can access, newest first, with the IDs of their members. Most tools act on one of them through their project_id argument.

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

Name	Required	Description	Default
`page`	No	Page number to show
`per_page`	No	Number of resources to return per page

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No	Meta data for pagination

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "created_at": {
+            "description": "Date of creation for the entity",
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "description": "Project ID",
+            "examples": [
+              1
+            ],
+            "type": "integer"
+          },
+          "members": {
+            "description": "List of team members that are part of this project",
+            "examples": [
+              [
+                1,
+                2,
+                3
+              ]
+            ],
+            "items": {
+              "type": "integer"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Project name",
+            "examples": [
+              "Luminous Guiding Tower"
+            ],
+            "type": "string"
+          },
+          "settings": {
+            "description": "Project settings",
+            "properties": {
+              "incident_merging_time_window": {
+                "default": 60,
+                "description": "Time window for incident merging in minutes",
+                "enum": [
+                  5,
+                  10,
+                  30,
+                  60,
+                  120,
+                  180
+                ],
+                "type": "integer"
+              },
+              "use_incident_ai": {
+                "default": true,
+                "description": "Whether to generate AI summaries for incidents",
+                "type": "boolean"
+              },
+              "use_incident_merging": {
+                "default": true,
+                "description": "Whether to use incident merging",
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "slug": {
+            "description": "Project slug",
+            "examples": [
+              "luminous-guiding-tower"
+            ],
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "Date of last update for the entity",
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "description": "Meta data for pagination",
+      "properties": {
+        "current_page": {
+          "examples": [
+            2
+          ],
+          "type": "integer"
+        },
+        "from": {
+          "examples": [
+            11
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "has_more_pages": {
+          "description": "Whether a next page exists, fetched with the page argument",
+          "type": "boolean"
+        },
+        "per_page": {
+          "examples": [
+            100
+          ],
+          "type": "integer"
+        },
+        "to": {
+          "examples": [
+            20
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior beyond that: results are paginated, sorted newest-first, and include member IDs, which tells the agent what ordering to rely on. It does not mention defaults or rate limits, but for a read-only list that is minor.

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 sentences, no redundancy, with the core action and sort order front-loaded before the cross-tool hint. Every clause carries information the agent can act on.

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 return shape need not be described, and annotations cover the safety profile. Ordering, pagination, and included member IDs are stated; only minor details like page-size defaults or total-count behavior are left to the schema.

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%, so page and per_page are already documented with defaults and a maximum. The description only alludes to pagination generically ('paginated list') without adding format or paging-strategy guidance beyond the schema, which is the baseline case.

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?

The description gives a specific verb and resource ('Get a paginated list of the projects'), states scope ('you can access'), ordering ('newest first'), and payload detail ('with the IDs of their members'). The second sentence positions it as the discovery tool for project IDs that other tools consume, which distinguishes it from get_project and the other list_* siblings.

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?

'Most tools act on one of them through their project_id argument' gives clear context for why an agent would call this, effectively framing it as the prerequisite lookup. It stops short of explicit when-not guidance (e.g. use get_project for a single project's details), so it is not a full 5.

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

All Phare tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?