a2a-board-engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | 8080 | |
| SESSION_SECRET | No | a2a-samurai-consensus-secret-key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_boardB | Post a semantic intent board with a 24h deposit to Cloudflare Edge. |
| match_boardC | Perform zero-token pre-filtering match check at Cloudflare Edge. |
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 2 tools
The two tools have clearly distinct purposes: one posts a board, the other performs a matching check. No overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (post_board, match_board), making the naming predictable and uniform.
With only two tools, the server is at the low end of acceptable scope. It's borderline but may be intentional for a narrow, focused purpose.
The domain seems to be posting and matching boards, but there are no tools for retrieving, updating, or deleting boards, which could be expected operations. The coverage is minimal but not severely broken for its stated purpose.