Skip to main content
Glama
robertobendi

WazziCode Godot

by robertobendi

project_manage

Stop a running Godot project and update its project.godot settings. Read or set configuration keys such as application/config/name.

Instructions

Project run/stop and project.godot settings.

Resource form: godot://project/info and godot://project/settings — prefer for active-session reads.

Ops: • stop() Stop the running project (game). Takes no params — call as project_manage(op="stop") or with params={}. Idempotent: succeeds with was_running=false if the project isn't running. Do NOT pass extra fields like force or reason inside params — only the registered keys are accepted (here, none). For multi-editor setups, pass session_id as a sibling of op/params, not inside params. • settings_get(key) Read a ProjectSettings key (e.g. "application/config/name"). • settings_set(key, value) Write a ProjectSettings key and persist to project.godot.

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
NameRequiredDescriptionDefault
opYes
paramsNo
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries full burden. It discloses key behaviors: stop is idempotent and returns was_running=false when not running, extra fields are rejected, session_id must be a sibling, and settings_set persists to project.godot. These go beyond minimal expectations and help the agent understand side effects and edge cases.

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 summary, resource form note, ops list, and call shape section. It is longer than necessary but every sentence adds useful detail; the idempotency and session_id notes are essential for correct invocation.

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?

Given the tool has three ops with differing parameter requirements and a generic input schema, the description provides comprehensive per-op semantics, call shape, and behavioral constraints. The presence of an output schema covers return values, so the description does not need to explain them. It is complete for the tool's complexity.

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?

Schema description coverage is 0%, so the description must compensate. It explains each op's parameters: stop takes none, settings_get takes a key, settings_set takes key and value, and session_id is separate. The canonical call shape is also defined, making parameter usage unambiguous.

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 clearly lists three operations (stop, settings_get, settings_set) and the resource types (project/info, project/settings). However, the summary line 'Project run/stop' is slightly ambiguous because there is no 'run' op, and the actual scope (stop + settings) is only fully clear after reading the ops list.

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?

Provides detailed call-shape guidance (op/params/session_id top-level, no extra params for stop, idempotency) and notes that resource forms are preferred for active-session reads. It does not explicitly differentiate when to use this tool vs siblings like project_run or game_manage for starting a project, but gives clear context for the stop and settings operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robertobendi/wazzicode-godot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server