Gibwork Sentinel
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gibwork_list_bountiesA | Discover and filter live bounties on the Solana Gibwork decentralized marketplace. |
| gibwork_get_bounty_detailsA | Get full description, requirements, creator info, and deadline for a specific Gibwork bounty ID. |
| gibwork_verify_escrowA | Verify the on-chain Solana token mint and escrow parameters for a Gibwork bounty before starting work. |
| gibwork_scaffold_workspaceA | Scaffold a local development directory with PR template, checklist, and metadata for a Gibwork bounty. |
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
Each tool targets a distinct stage of the bounty workflow: discovery, detail lookup, escrow verification, and workspace setup. There is no meaningful overlap between list, get, verify, or scaffold.
All tool names follow the same gibwork_<verb>_<noun> convention: list_bounties, get_bounty_details, verify_escrow, scaffold_workspace. The pattern is uniform and predictable.
Four tools is a tight, well-scoped set for the server's apparent purpose of safely discovering and preparing for Gibwork bounties. Each tool serves a necessary function without redundancy.
The toolset covers the full pre-work lifecycle: find bounties, inspect details, verify escrow, and scaffold a workspace. Post-submission actions like submitting or claiming work are absent, but they appear outside the server's stated scope as a pre-work sentinel.