agent-billboard-mcp

Overview Schema Source Related Servers Discussions Admin

Clear the message

clear_message

DestructiveIdempotent

Clear the current billboard message in a single transaction while preserving posting rights and staked amount. Only works if your wallet holds the slot; logs reasoning and supports dry-run proposals.

Instructions

Empty the billboard message. Only works while this wallet holds the slot; otherwise the call is refused before anything is signed. Posting rights and the staked amount are unchanged. One transaction. Logged with your reasoning. Under AUTO_BID=false this returns status "proposed" and signs nothing; call approve_proposal to sign.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`reason`	No	Human-readable detail for refused and failed outcomes.
`status`	Yes
`expires_at`	No	Set when status is "proposed": the proposal cannot be approved after this time.
`signatures`	Yes
`proposal_id`	No	Set when status is "proposed": pass it to approve_proposal to sign.
`current_poster`	Yes
`existing_bytes`	Yes	Bytes on the billboard when this call read it (what a clear removes).
`you_are_poster`	Yes
`billboard_after`	No
`transactions_sent`	Yes
`current_amount_sol`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: one transaction, refusal before signing, unchanged posting rights and staked amount, logging with reasoning, and the AUTO_BID=false status behavior. It aligns with the destructiveHint and adds meaningful detail.

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 useful information: the core action, precondition, state invariants, transaction count, logging requirement, and conditional flow. It is detailed yet tightly structured, with the main action front-loaded.

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?

The description covers the operation's precondition, side effects, signing behavior, and the alternative action in AUTO_BID=false mode. With an output schema present and only one well-documented parameter, nothing essential is missing for an agent to invoke it correctly.

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?

The single parameter reasoning is already fully described in the schema, including required status, max length, and its purpose. The description mentions logging with reasoning, which echoes the schema rather than adding new semantic detail, so baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Empty the billboard message.' This clearly distinguishes clear_message from its siblings like append_message and read_billboard, and goes beyond merely restating the tool name.

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 gives explicit conditions: it only works while the wallet holds the slot, and otherwise the call is refused before signing. It also provides a concrete alternative by instructing to call approve_proposal when AUTO_BID=false returns status 'proposed'.

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

Deploy Server