godot-omni

Overview Schema Source Related Servers Discussions Admin

session_manage

Lists connected Godot editor sessions with metadata including version, scene, and play state. Pings a session to verify it remains active.

Instructions

Session listing.

Resource form: godot://sessions — prefer for resource-aware clients.

Ops: • list() List every connected Godot editor with metadata: session_id, short name, godot_version, project_path, plugin_version, server_version, editor_pid, server_launch_mode, current_scene, play_state, readiness, connected_at, last_seen, is_active. The response also carries the server-global exclude_domains (tool domains not registered on this server via --exclude-domains).

Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`op`	Yes
`params`	No
`session_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.0.9Sep 19, 2026
- removedInput schema / properties / op / const
```
Removed value: -"list"
```
- addedInput schema / properties / op / enum
```
Added value: +[
+  "list",
+  "ping"
+]
```
First observedv4.1.0Sep 17, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden and does disclose substantial behavior: the full metadata field list for list(), the server-global exclude_domains field, and the canonical vs. flat call-shape compatibility. However, the ping operation is completely undocumented, and there is no explicit statement about side effects or read-only behavior beyond the word 'listing.'

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?

The description is well-structured with a clear 'Ops' bullet, a concise resource-form note, and a detailed but relevant metadata list. It is front-loaded with the core 'Session listing' purpose, though the omission of ping makes the structure feel incomplete rather than intentionally concise.

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

Completeness2/5

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

The list() path is described in detail, but the tool is a dual-op tool according to the schema and the description covers only one op. The missing ping semantics, undefined session_id usage, and lack of differentiation from the sibling ping tool leave an agent without enough information to use the full tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only explains the call-shape convention and leaves session_id and params semantically undefined. The op parameter's valid values are mentioned only in the schema, and the meaning of the 'ping' op is not explained at all.

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

Purpose3/5

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

The description clearly identifies the list() operation and the session metadata it returns, which establishes a specific resource and action. However, the tool is named session_manage and the schema also exposes a 'ping' operation that the description never mentions, so the stated purpose ('Session listing') is incomplete and does not cover the full tool surface.

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

Usage Guidelines2/5

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

The only usage guidance is 'prefer for resource-aware clients,' which addresses transport style rather than when to choose this tool over alternatives. It provides no guidance on when to use list() versus ping(), nor how session_manage relates to sibling tools like session_activate or ping.

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