Skip to main content
Glama

Wall grid

wall_grid

The Wall — a 10,000-tile grid at /wall/. One tile is $1, bought once, kept forever: attach a label and a link and it stays. Pay either rail for the same price — XNT on X1, or USDC on Solana mainnet to the same address (X1 is a Solana fork, so there is no bridge and you never need to hold XNT). Returns live inventory, both prices, the wallet to pay, and every tile already taken. No subscription and no expiry. Outbound links are rel="sponsored nofollow noopener".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wall_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoOptional — get an exact quote for this many tiles (1-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses permanence, no subscription or expiry, two payment rails, no bridge/no need to hold XNT, the returned fields, and outbound link rel attributes. It still does not explicitly state that the tool itself does not purchase tiles, nor does it mention permission or rate-limit behavior.

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

Conciseness3/5

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

The description is several sentences long and spends substantial space on payment-rail mechanics and link attributes while omitting the only parameter. It is mostly informative, but it is not front-loaded with the tool action or quote behavior.

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 low-complexity tool with one optional parameter and no output schema, the description covers the key return fields and economic terms well. The main gaps are not clarifying the count-based quote and not explicitly distinguishing inspection from purchase execution.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents count as an optional 1-100 tile quote. The description adds no count-specific meaning and never mentions the parameter at all, so it adds no value beyond the schema for parameter semantics.

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 names the Wall grid, its 10,000-tile inventory, the $1 permanent-tile model, and explicitly states that it returns live inventory, both prices, the payment wallet, and taken tiles. It lacks a leading action verb and mixes product/purchase mechanics with the tool's return scope, but the read/quote function is still identifiable.

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?

There is no explicit when-to-use or when-not-to-use guidance, no named alternatives, and no statement that the optional count parameter produces a quote. The agent must infer that this tool is for checking wall inventory and prices before paying.

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.

Resources