agent-billboard-mcp

by yourmatematt

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Acquire posting rights

acquire_posting_rights

Destructive

Place a bid on a Solana billboard slot to post your message, with dry-run validation and audit logging.

Instructions

Bid for the billboard slot and optionally post a message in the same transaction. The bid must be at least 1% over the current amount; the displaced poster gets their stake back plus half the increase, the creator gets the other half; acquiring clears the message. Defaults bid_sol to the minimum. Always call read_billboard first and try dry_run: true before bidding. The server enforces MAX_BID_SOL and DAILY_CAP_SOL before signing and logs every outcome with your reasoning. Under AUTO_BID=false this returns status "proposed" with a proposal_id and signs nothing; call approve_proposal to sign.

Input Schema

TableJSON Schema

Name	Required	Description
`bid_sol`	No	Bid in SOL as a decimal string, e.g. "0.105". Defaults to the current program minimum (1% over the current amount, rounded down). Must be within MAX_BID_SOL and DAILY_CAP_SOL.
`dry_run`	No	When true, compute every figure and sign nothing. Works in read-only mode. Use it before a real bid.
`message`	No	Message to post once the slot is yours. Acquiring clears the previous message. Measured in UTF-8 bytes (max 4096); longer messages are sent as several transactions.
`reasoning`	Yes	Why you are doing this, in plain language. Written verbatim to the operator activity log beside the transaction signature. Required. At most 2000 characters.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`limits`	Yes
`reason`	No	Human-readable detail for refused and failed outcomes.
`status`	Yes
`bid_sol`	Yes	The bid this call evaluated (given, or the minimum).
`expires_at`	No	Set when status is "proposed": the proposal cannot be approved after this time.
`signatures`	Yes	Transaction signatures, in the order they landed.
`proposal_id`	No	Set when status is "proposed": pass it to approve_proposal to sign.
`message_bytes`	Yes
`current_poster`	Yes
`you_are_poster`	Yes	True when the wallet already holds the slot; use append_message instead.
`billboard_after`	No
`minimum_bid_sol`	Yes
`transactions_sent`	Yes
`current_amount_sol`	Yes
`creator_receives_sol`	No
`transactions_planned`	Yes
`previous_holder_receives_sol`	No	Refund to the displaced poster: their stake plus half the increase.
`if_outbid_at_minimum_you_receive_sol`	No	What you get back if someone later outbids you at the minimum.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the annotations by detailing financial side effects (displaced poster gets stake back plus half the increase, creator gets the other half), message clearing, server-enforced limits (MAX_BID_SOL, DAILY_CAP_SOL), unconditional logging of reasoning, and the no-sign 'proposed' path when AUTO_BID=false. There is no contradiction with the readOnlyHint=false and destructiveHint=true annotations; the behavior described aligns with those hints.

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?

Every sentence carries necessary operational information, and the description is front-loaded with the primary action and then the key constraints and sequencing. It is dense but not padded; the length is justified by the financial side effects, mandatory preconditions, and branching auto-sign behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a bid-with-message acquisition flow that includes fee distribution, server limits, dry-run behavior, message clearing, and the AUTO_BID=false branch, the description is remarkably complete. The presence of an output schema plus this description gives an agent everything needed to invoke the tool correctly and to understand what will happen before signing.

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

Parameters5/5

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

Even though the schema already covers 100% of parameters, the description enriches them with actionable semantics: the minimum bid rule, defaulting bid_sol to the minimum, dry_run computing figures without signing, message clearing and UTF-8 byte sizing, and reasoning being written verbatim to the operator activity log. These details materially improve an agent's ability to set parameters correctly.

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 names a specific action ('Bid for the billboard slot and optionally post a message') with concrete resource details and distinguishes its combined bid-and-post behavior from siblings like read_billboard, append_message, and approve_proposal. It unmistakably states what the tool does without ambiguity. It also adds critical specifics like 'acquiring clears the message', making the core purpose very clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when and how to use the tool: 'Always call read_billboard first and try dry_run: true before bidding' and explains the alternate flow under AUTO_BID=false with a pointer to approve_proposal. This is direct when-to-use guidance with a clear alternative. It makes no misleading claims and fully routes decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server