Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

Who am I

whoami
Read-onlyIdempotent

Get your user, role, organization, permissions and the projects you can access. Call it first: most tools act on one of these projects through their project_id argument, and your permissions decide which tools you can use.

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": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
userYes
projectsYesProjects the user can access
permissionsYesPermissions of the role, each tool requires one of them
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "organization": {
+      "properties": {
+        "id": {
+          "description": "Organization ID",
+          "type": "integer"
+        },
+        "name": {
+          "description": "Organization name",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    "permissions": {
+      "description": "Permissions of the role, each tool requires one of them",
+      "items": {
+        "enum": [
+          "monitors:read",
+          "monitors:write",
+          "reports:read",
+          "incidents:read",
+          "incidents:write",
+          "incidents:moderate",
+          "maintenance_windows:read",
+          "maintenance_windows:write",
+          "status_pages:read",
+          "status_pages:write",
+          "projects:read",
+          "projects:write",
+          "projects:all",
+          "alert_rules:read",
+          "alert_rules:write",
+          "integrations:read",
+          "integrations:write",
+          "members:read",
+          "members:write",
+          "api_keys:write",
+          "organization:write",
+          "billing:write"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "projects": {
+      "description": "Projects the user can access",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Project ID, the project_id argument of the other tools",
+            "type": "integer"
+          },
+          "name": {
+            "description": "Project name",
+            "type": "string"
+          },
+          "slug": {
+            "description": "Project slug",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "slug"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "user": {
+      "properties": {
+        "email": {
+          "description": "User email address",
+          "type": "string"
+        },
+        "id": {
+          "description": "User ID",
+          "type": "integer"
+        },
+        "role": {
+          "description": "Role of the user in the organization, it grants the permissions",
+          "enum": [
+            "viewer",
+            "responder",
+            "member",
+            "admin"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "email",
+        "role"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "user",
+    "organization",
+    "permissions",
+    "projects"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/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 real behavioral context beyond them: it enumerates the returned identity/permission payload and warns that the result determines which sibling tools are usable and which project_id values are valid.

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, zero filler, and every clause carries decision-relevant information. Front-loading the sequencing advice ahead of the payload description would be marginally better, but nothing is wasted or redundant.

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?

For a zero-parameter, read-only, output-schema-backed identity tool, the description covers purpose, sequencing, and downstream consequences of the result. Annotations handle the safety profile and the output schema handles return values, so no agent-critical information is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. It is held slightly at 3 because the description instead spends its parameter-adjacent text explaining how OTHER tools' project_id relates to this output, not this tool's own inputs.

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?

Uses a specific verb ("Get") plus an enumerated resource set — user, role, organization, permissions, accessible projects — so the agent knows exactly what comes back. The possessive "your" implicitly separates it from get_user/list_users/list_projects, but no sibling is named explicitly, leaving that differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it first" is an explicit ordering directive, and the description gives the reason: most tools act on a project via their project_id argument, and permissions gate which tools are callable at all. This turns a bootstrapping step into an actionable workflow rule rather than a vague suggestion.

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

All Phare toolsInspect
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