buttonwall
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wall_statusA | How full The Button Wall is right now, plus pricing rules. The wall is 1000×1000 px; spots are rented in 10×10 px blocks. |
| quote_spotB | Price for a button of a given size and plan, and whether that exact position is free. |
| find_free_spotsB | Free positions that fit a button of the given size, nearest to a preferred point first (default: the centre of the wall). |
| create_checkout_linkA | Creates a Stripe checkout link for a new button. Nothing is charged by this call: the link must be opened and paid by the human buyer, and the button goes live only after a person at The Button Wall reviews it (full refund if rejected). Confirm size, position, plan, price, text and link with the user before calling. Call once per purchase: checkout links are rate-limited (10 per 10 minutes). |
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 4 tools
The four tools target distinct steps in the purchase flow, but quote_spot (price + exact availability) overlaps with find_free_spots (available positions) and get_wall_status (fullness + pricing rules). Descriptions help clarify boundaries, but an agent could still hesitate between quote_spot and find_free_spots when checking a specific location.
All tool names follow a consistent snake_case verb_noun pattern: create_checkout_link, get_wall_status, quote_spot, find_free_spots. The convention is predictable and readable throughout.
Four tools form a tight, purposeful set for a niche purchasing workflow: discovery (find_free_spots), pricing/availability (quote_spot), context (get_wall_status), and purchase initiation (create_checkout_link). Nothing feels redundant or missing from the core flow.
The surface covers the essential pre-purchase and checkout steps, but lacks post-purchase operations such as checking order/review status or viewing one's existing buttons. These are minor gaps an agent can work around or that may be intentionally out of scope.