Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

read_resource

Inspect properties of a Godot Resource file by providing its res:// path to understand resource contents and settings.

Instructions

Read properties of a Godot Resource file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "read_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a pure read but never confirms there are no side effects, says nothing about what happens when the path is missing or invalid, and does not indicate whether raw file text, parsed properties, or a structured object is returned.

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?

A single short sentence that front-loads the verb and resource with zero filler. It is efficiently written, though the brevity borders on under-specification rather than optimal density.

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

Completeness3/5

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

For a one-parameter read tool with a fully documented schema and no output schema, the description covers the essentials. It is still thin on error behavior and return shape, which matter for an agent deciding whether to call it on an arbitrary res:// path.

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?

With a single parameter at 100% schema description coverage, the schema already explains that 'path' is a 'res:// path to the resource'. The description adds no further syntax, constraints, or examples, so the baseline of 3 applies.

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 gives a specific verb ('Read') and resource ('properties of a Godot Resource file'), which is enough to distinguish it from siblings like read_script or read_shader that target other file kinds. It falls short of 5 because it never explicitly contrasts itself with edit_resource or get_resource_preview.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of when to prefer edit_resource, get_resource_preview, or the script/shader readers. The intended use is only inferable from the tool name and the word 'Read'.

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