Skip to main content
Glama
GuiaIA MCP Server

GuiaIA MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SNAPSHOTNoPath to a trusted snapshot JSON file, passed via --snapshot, for read-only local mode.
RCON_PORTNoRCON port for the Minecraft server, passed via --rcon-port (default 25575).
PYTHONPATHNoAbsolute path to the GuiaIA/src directory, required to run the MCP server from a source checkout.
RCON_PASSWORD_FILENoPath to a local file containing the Minecraft RCON password, passed via --rcon-password-file.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read-only observations and planning. No game or server mutation tools are exposed.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
guia_statusA

Read sanitized status; does not reveal player names or change the world.

guia_performanceB

Read available metrics; absent data stays null (never guessed).

guia_diagnoseB

Interpret existing telemetry and propose safe next steps; never applies fixes.

guia_world_observeA

Read a recent, privacy-safe aggregate sample of one already-loaded chunk; no player identities or world changes.

guia_plan_gatherA

Parse a Spanish request into an explicit non-executing plan. No gameplay actions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

The tools are mostly distinct: diagnose interprets telemetry, performance reads metrics, status reads sanitized status, world_observe reads chunk samples, and plan_gather parses requests into plans. However, diagnose, performance, status, and world_observe all overlap as read-only observability tools, which could cause some confusion for an agent deciding which read tool to use.

Naming Consistency3/5

All tools share the guia_ prefix, which provides some consistency. But the suffixes mix verbs, nouns, and verb_noun patterns (diagnose, performance, plan_gather, status, world_observe), making the naming convention only partially predictable.

Tool Count5/5

Five tools is well-scoped for a read-only diagnostics and planning server. Each tool appears to have a specific role, and the set is neither too thin nor too heavy.

Completeness4/5

For a read-only server that explicitly avoids applying fixes or modifying the world, the surface covers diagnosis, performance metrics, status reading, world observation, and planning. Minor gaps might exist around discovering available telemetry sources or detailed metric queries, but the core lifecycle is covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues