Skip to main content
Glama
kitao

pyxel-mcp

by kitao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pyxel_info

Read-onlyIdempotent

Retrieve installed Pyxel versions, file paths, examples, and resource URIs to enable AI models to verify and run retro game programs.

Instructions

Report installed versions, paths, examples, and Pyxel resource URIs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
errorsYes
examplesNo
resourcesNo
stubs_pathNo
pyxel_versionNo
python_versionNo
pyxel_mcp_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.3.0
    • addedOutput schema / $defs
      Added value: +{
+  "ExampleInfo": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Description"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "path": {
+        "title": "Path",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "path"
+    ],
+    "title": "ExampleInfo",
+    "type": "object"
+  },
+  "ToolErrorRecord": {
+    "additionalProperties": false,
+    "properties": {
+      "frame": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Frame"
+      },
+      "message": {
+        "title": "Message",
+        "type": "string"
+      },
+      "path": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Path"
+      },
+      "phase": {
+        "title": "Phase",
+        "type": "string"
+      },
+      "traceback": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Traceback"
+      }
+    },
+    "required": [
+      "phase",
+      "message"
+    ],
+    "title": "ToolErrorRecord",
+    "type": "object"
+  }
+}
    • addedOutput schema / additionalProperties
      Added value: +false
    • addedOutput schema / properties / errors
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/ToolErrorRecord"
+  },
+  "title": "Errors",
+  "type": "array"
+}
    • addedOutput schema / properties / examples
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/ExampleInfo"
+  },
+  "title": "Examples",
+  "type": "array"
+}
    • addedOutput schema / properties / ok
      Added value: +{
+  "title": "Ok",
+  "type": "boolean"
+}
    • addedOutput schema / properties / python_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Python Version"
+}
    • addedOutput schema / properties / pyxel_mcp_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pyxel Mcp Version"
+}
    • addedOutput schema / properties / pyxel_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pyxel Version"
+}
    • addedOutput schema / properties / resources
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "title": "Resources",
+  "type": "object"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / stubs_path
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Stubs Path"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "ok",
+  "errors"
+]
    • changedOutput schema / title
      Previous value: -"pyxel_infoOutput"New value: +"PyxelInfoResult"
  2. First observedv0.8.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral detail by specifying exactly what the tool reports, which is beyond what the empty input schema and annotations reveal.

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

Conciseness5/5

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

The description is a single sentence with the verb and key output categories front-loaded. Every word contributes meaning, and there is no redundancy or filler.

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

Completeness4/5

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

For a zero-parameter, read-only, non-destructive tool with an output schema and strong annotations, the description is sufficient for an agent to select and invoke it correctly. The only minor gap is the lack of explicit guidance about when to prefer it over sibling tools, but this does not hinder correct invocation.

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

Parameters4/5

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

The tool has zero parameters, so the baseline of 4 applies. There is nothing for the description to explain about parameters, and the description correctly focuses on the tool's output rather than input semantics.

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

Purpose5/5

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

The description uses a specific verb ('Report') and names an exact set of outputs: installed versions, paths, examples, and Pyxel resource URIs. This clearly distinguishes it from sibling read_* tools that target game assets such as palettes, images, tilemaps, and audio.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance or mention of alternatives. However, the tool's purpose is strongly implied by its name and content: use it to introspect the Pyxel environment rather than to execute or validate game resources. The guidance is implicit, not explicit.

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