Skip to main content
Glama
Sign In
Phaser Editor MCP Server

Phaser Editor MCP Server

Official
by phaserjs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

assets-get-texture-size

Retrieve the pixel dimensions (width and height) of a texture asset by specifying its key and optional frame.

Instructions

Get the binary data of a texture.

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": "assets-get-texture-size"
  }
}

Input Schema

NameRequiredDescriptionDefault
textureNoThe texture of the game object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action (get binary data) without describing the output format, side effects, or any constraints. The tool name suggests a size return, but the description implies binary data, creating confusion.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it is inaccurate relative to the tool name. Conciseness alone does not compensate for misleading content. The description should be clarified to match the tool's actual function.

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

Completeness1/5

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

Given the complexity of the tool (nested object parameter, likely binary output) and the absence of an output schema and annotations, the description is severely incomplete. It fails to explain what the return value is, how to interpret it, or how this tool differs from similar siblings.

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?

The input schema has 100% description coverage for the single parameter 'texture' and its nested properties 'key' and 'frame.' The description adds no further semantic information beyond the schema, so it meets the baseline for parameter explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get the binary data of a texture,' but the tool name is 'assets-get-texture-size,' which implies retrieving the size (dimensions) of a texture. This mismatch is misleading and fails to clarify the tool's actual purpose. Additionally, a sibling tool 'assets-get-texture-binary' exists, further confusing the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not explain the difference between this tool and the sibling 'assets-get-texture-binary,' nor does it mention any prerequisites or conditions for use.

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