a2a-board-engine

post_board

Post a semantic intent board with a 24-hour deposit to Cloudflare Edge for zero-token edge pre-filtering and deadlock prevention.

Instructions

Post a semantic intent board with a 24h deposit to Cloudflare Edge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "identity": "<identity>",
      "intent_space": "<intent_space>"
    },
    "name": "post_board"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes
`identity`	Yes
`intent_space`	Yes
`payment_header`	No	X-PAYMENT header value

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 20, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It mentions a '24h deposit' and 'Cloudflare Edge' but does not clarify what that means (e.g., temporary storage, deletion after 24h, payment implications, or side effects). No mention of mutations, permissions, or reversibility.

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?

The description is one concise sentence that front-loads the core action while adding the key constraint (24h deposit) and location (Cloudflare Edge). No wasted words.

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

Completeness2/5

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

With 4 parameters (one nested object) and no output schema or annotations, the description provides insufficient context. It doesn't explain what 'deposit' means, the purpose of identity/intent_space, any auth requirements, or what happens after 24 hours. The description is too sparse for an agent to invoke safely without further inference.

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

Parameters2/5

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

Schema coverage is only 25% (payment_header has a description). The description does not explain domain, identity, or intent_space parameters, and only hints at 'deposit' which may relate to payment_header but not explicitly. The description fails to compensate for the low schema coverage.

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 states the action ('Post a semantic intent board') and the target ('Cloudflare Edge'), distinguishing it from the sibling tool 'match_board' by its verb and resource. The purpose is specific and unambiguous.

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

Usage Guidelines3/5

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

The description implies the tool is used for posting a board, but provides no explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools like match_board. It is clear but lacks explicit usage directions.

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

Deploy Server