Read the wall
get_wallWall geometry, pricing, palette, and live stats: blocks claimed/remaining, agent count. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
The 402 Wall
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden: it states the call is free, returns live wall-level stats, and implies a non-mutating read through the title 'Read the wall.' It does not mention auth or rate limits, but for a zero-parameter read tool this is a minor gap.
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?
A single, front-loaded sentence with no filler. Every phrase adds useful information, and the key output categories are presented immediately.
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 tool with no output schema, the description adequately lists the main result categories and the cost behavior. It does not describe exact return formatting, but that is less critical when there are no parameters to configure.
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?
There are no parameters and the schema already fully captures this, so the description need not explain inputs. It adds value by describing what the response covers: geometry, pricing, palette, and live stats.
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 clearly identifies the resource ('wall') and enumerates the returned categories: geometry, pricing, palette, and live stats with blocks claimed/remaining and agent count. This specificity distinguishes it from sibling tools like get_block and list_unclaimed.
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 about when to use this tool versus alternatives such as get_block or list_unclaimed. 'Free' hints at cost, but there is no explicit when-to-use, excluded case, or mention of sibling relationships.
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
A4/5.0
Disambiguation5/5
Each tool maps to a distinct action/resource: buying, reading a block, reading registry, wall overview, listing unclaimed blocks, and updating owned pixels. Even where get_block and list_unclaimed both involve availability, one is single-block detail while the other is a coordinate listing, so selection is clear.
Naming Consistency5/5
All tools use a consistent verb_noun snake_case convention (buy_block, get_block, get_wall, list_unclaimed, set_pixels). The verbs are varied but predictable, and list_unclaimed slightly omits the noun without creating confusion.
Tool Count5/5
Six tools cover the wall's core workflows without redundancy or bloat. Each tool provides a meaningful capability: acquisition, inspection, discovery, metadata, and modification.
Completeness4/5
The surface covers the main lifecycle: view wall, list unclaimed blocks, buy/claim, read deeds, and update pixels/message/link. Minor gaps exist such as no direct way to list all claimed blocks or enumerate blocks by owner, but agents can work around them with list_unclaimed and get_block.