Godot AI

Overview Schema Source Related Servers Discussions Admin

Session Activate

session_activate

Selects the active Godot editor session for subsequent tool calls using an exact ID or project name substring. Resolves ambiguity by requiring a unique match, returning candidates when unclear.

Instructions

Set the active Godot editor session for subsequent tool calls.

Accepts either an exact session_id or a substring hint matched against the session's short name (project folder basename), project_path, or session_id. An exact id match always wins; a substring must resolve to exactly one session or the tool returns an error listing the candidates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	An exact session id (``<project-slug>@<16hex>``, e.g. ``my_game@7f9c3a10d8e426b1``, from ``session_manage`` with op="list") OR a substring hint like a project folder name ("test_project", "my_game").

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.2.5Sep 3, 2026

changedInput schema / properties / session_id / description

Previous value: -"An exact session id (``<project-slug>@<4hex>``, e.g.\n``my_game@a3f2``, from ``session_manage`` with op=\"list\")\nOR a substring hint like a project folder name\n(\"test_project\", \"my_game\")."New value: +"An exact session id (``<project-slug>@<16hex>``, e.g.\n``my_game@7f9c3a10d8e426b1``, from ``session_manage`` with op=\"list\")\nOR a substring hint like a project folder name\n(\"test_project\", \"my_game\")."

Addedv3.1.4Aug 10, 2026
Removedv3.0.7Jul 26, 2026

Changed1 schema field changedv3.0.3Jul 16, 2026

changedInput schema / properties / session_id / description

Previous value: -"An exact session id (e.g. UUID from ``session_manage``\nwith op=\"list\") OR a substring hint like a project folder name\n(\"test_project\", \"my_game\")."New value: +"An exact session id (``<project-slug>@<4hex>``, e.g.\n``my_game@a3f2``, from ``session_manage`` with op=\"list\")\nOR a substring hint like a project folder name\n(\"test_project\", \"my_game\")."

First observedv2.9.1Jul 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and mostly succeeds: it explains exact-match precedence, which fields substring hints match against, and the ambiguity error listing candidates. It could add a note that the previously active session is replaced, but the state-transition is already clear from 'Set the active...'

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?

The key statement is front-loaded in the first sentence, followed by two compact sentences that fully explain matching rules. No filler or redundant repetition of the schema.

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 one-parameter state-selection tool with an output schema and full schema parameter coverage, the description is sufficient: it explains what the operation does, how the parameter is interpreted, and what happens on failure. Nothing essential is missing.

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

Parameters5/5

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

The parameter schema provides the format and examples, and the description adds important semantics beyond it: matching against short name/project_path/session_id, exact-id precedence, and the requirement that a substring resolve to exactly one session. This resolves ambiguity that the schema alone leaves open.

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 opens with a specific verb and object: 'Set the active Godot editor session for subsequent tool calls.' This clearly distinguishes session_activate from sibling tools like session_manage, which would handle listing/creating/managing sessions rather than selecting the active one.

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?

It states the context of use: before other tool calls that should target a chosen editor session. It does not name an alternative or an explicit when-not-to-use, but the 'subsequent tool calls' framing plus the exact/substring semantics give enough guidance for selection.

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