Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_resource

Create Godot resource files to store game assets, configurations, and data. Enables AI assistants to programmatically generate and manage resources within Godot engine projects.

Instructions

Create resource file. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions '(Compatibility tool)' suggesting legacy or specific behavioral mode, but provides no details on side effects, persistence, file system interactions, or what the timeoutMs parameter implies about network/file I/O behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (two fragments), which prevents information overload, but the '(Compatibility tool)' aside consumes space without delivering value. The description is front-loaded but suffers from under-specification rather than efficient precision.

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?

Given two undocumented parameters and no output schema or annotations, the description is inadequate. It doesn't explain the return value, error conditions, or the relationship between the connection-oriented parameters and the file creation operation.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters (timeoutMs and autoConnect). The description fails entirely to explain what timeoutMs measures (connection timeout? file write timeout?), what autoConnect connects to, or why a 'resource file creation' operation involves connection semantics.

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?

States basic action (create) and target (resource file), which minimally distinguishes it from siblings like 'add_resource' (implies file creation vs. adding to scene). However, the cryptic '(Compatibility tool)' parenthetical adds confusion without explanation, and it doesn't clarify the specific resource types or scope compared to 'edit_resource' or 'read_resource'.

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?

Provides no guidance on when to use this versus 'add_resource', 'edit_resource', or 'read_resource'. The 'Compatibility tool' label hints at a specific use case but fails to explain what compatibility scenario warrants its use over alternatives.

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

Deploy Server

Other Tools