Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_resource_preview

Retrieve a base64 preview image for a Godot resource file by specifying its res:// path, useful for inspecting resources without opening them.

Instructions

Get a preview image (base64) for a 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": "get_resource_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose the return format (base64-encoded image, which matters since there is no output schema), but says nothing about what happens for non-image resources, whether the preview is downscaled, size limits, or error behavior.

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 with the output encoding front-loaded, and nothing superfluous. Its brevity is close to under-specification, which keeps it from a top score.

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 simple one-parameter read tool with no output schema, the description covers what the tool returns at a high level (base64 preview image). It falls short on edge-case behavior and limitations that would let an agent call it confidently when the resource is not a renderable image.

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 one parameter and 100% schema description coverage ('res:// path to the resource'), the schema already conveys the parameter's meaning. The description's phrase 'for a resource file' adds only slight reinforcement and no format or constraint detail beyond the schema.

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?

States a specific verb ('Get') and resource ('preview image (base64) for a resource file'), which distinguishes it from read_resource/create_resource/edit_resource by naming the visual-preview output. It does not explicitly name a sibling or contrast behavior, keeping it just short of a 5.

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, when-not-to-use, or alternative-tool guidance. An agent must infer from the description alone that this is for image previews rather than reading file content with read_resource, and no prerequisites (e.g., only image-type resources) are stated.

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