unity-ludometry-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_statusA | Report this server's version, the agent protocol version it speaks, where it keeps its data (the profile root), and what the connected MCP client supports. Read-only; safe to call at any time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool there is nothing to confuse it with, so selection risk is effectively zero. However, the tool's purpose (server status reporting) gives no signal about what the server's actual domain is, leaving the set trivially unambiguous but uninformative.
The lone tool uses a clear snake_case verb_noun-style name (server_status) that reads well and follows a common convention. With only one tool there is no second name to establish or violate a pattern, so consistency can only be partially assessed.
A single read-only status tool is far too thin for a server whose name implies a ludometry (game/play measurement) domain. One tool cannot plausibly represent the intended scope, making this an extreme under-provision of the surface.
The surface contains only a diagnostic status endpoint and no domain operations whatsoever — no create, read, update, or delete of any ludometry-related resource. An agent has no way to accomplish anything beyond checking server health, so the toolset is severely incomplete.