Phare

Get a project

get_project

Read-onlyIdempotent

Get a project by ID, with the IDs of its members and its incident settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "get_project"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	ID of the project to show

Output Schema

Name	Required	Description
`id`	No	Project ID
`name`	No	Project name
`slug`	No	Project slug
`members`	No	List of team members that are part of this project
`settings`	No	Project settings
`created_at`	No	Date of creation for the entity
`updated_at`	No	Date of last update for the entity

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedNov 7, 2026

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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one piece of real context beyond that: the response bundles member IDs and incident settings. It does not mention permissions, error behavior for unknown IDs, or depth of the incident settings payload.

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?

One sentence, front-loaded with the verb and resource, with the returned extras trailing as a qualifier. Every clause earns its place and nothing is padded.

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 one required parameter at full schema coverage, rich read-only annotations, and an output schema that documents return values, the description does not need to explain much more. Its only mild gap is not stating what happens when the project ID does not exist.

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% for the single parameter, so the schema already explains that project_id is the ID of the project to show. The description adds no syntax, format, or lookup guidance beyond that, so the baseline of 3 applies.

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 ("Get a project") and adds scope ("by ID"), which distinguishes it cleanly from list_projects in the sibling set. It stops short of explicitly naming the alternative, but the singular-plus-ID phrasing makes the distinction obvious.

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: 'by ID' signals this is the single-record lookup and that a project_id is required. There is no explicit when-to-use guidance, no statement of when to prefer list_projects or a search, and no prerequisites noted.

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?