Get the overview raster
get_overviewThe coarse top-surface raster behind the homepage's isometric view, plus a small ASCII preview.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
WOCLUB Cube Playground
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the output contents (raster and ASCII preview), giving some transparency. However, there is no mention of side effects, permissions, or error behavior, and the lack of annotations means the description carries the full burden.
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, concise sentence that directly states the tool's output. It contains no unnecessary words or redundant details.
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?
Given the tool has no parameters and no output schema, the description sufficiently explains what the tool provides. It could be slightly more detailed about the raster format, but the essential information is present.
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 and the schema coverage is 100%, so the baseline score is 4. The description does not need to explain parameters that do not exist.
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?
The description clearly indicates the tool returns a coarse top-surface raster and an ASCII preview, which distinguishes it from other getters like get_cube or get_region. However, it lacks an explicit verb like 'returns' and could be more direct about the resource being retrieved.
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?
No guidance is provided on when to use this tool instead of alternatives like get_world_stats or get_region. The description does not mention any scenario or context that would lead an agent to select this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a distinct purpose: querying single cubes, regions, overviews, stats, and performing single or bulk modifications. Even though build overlaps with individual place/remove operations, its batch nature differentiates it clearly.
Naming Consistency5/5
All tools follow a consistent lowercase_with_underscores naming convention. Verbs clearly indicate actions (get, place, remove, clear, fill, build), making the toolset predictable and easy to navigate.
Tool Count5/5
With 9 tools, the set is well-scoped for a cube world manipulation server. It provides both granular operations (place_cube, remove_cube) and higher-level bulk operations (build, fill_box, clear_mine) without unnecessary redundancy.
Completeness5/5
The toolset covers the full lifecycle of cube manipulation: querying (get_cube, get_region, get_overview, get_world_stats), creating (place_cube, build, fill_box), and deleting (remove_cube, clear_mine). No essential operations for a Minecraft-like environment are missing.