oneshot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PACKS_DIR | No | Local fallback packs directory | ../packs |
| ONESHOT_SITE_URL | No | Base URL used to build pack/buy links | https://oneshotpacks.com |
| ONESHOT_CATALOG_URL | No | Remote catalog URL tried first | https://oneshotpacks.com/catalog.json |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_packsA | Search the OneShot catalog of receipt-verified agent build packs by keyword (stack, problem, or niche -- e.g. "stripe billing subscription" or "offline sync"). Returns matching packs with title, one-liner, price, verification status stated exactly as the receipt supports (e.g. "3 of 3 clean-room runs passed", or "unverified" if no receipt exists yet -- never invented), a receipt summary, and the storefront URL. Does not rank or editorialize any pack as "best" -- describes each match and leaves the choice to the caller. |
| get_packA | Full detail for one OneShot pack by slug: what you get, architecture-decision highlights, the scale envelope, FAQ, the exact receipt facts (per-check pass/fail, model, token and wall-time cost) when the pack has been verified, price, a refund-policy pointer, and the buy URL. Reports 'unverified' honestly when no execution receipt exists yet -- never implies a verification the receipt doesn't support. |
| list_packsA | The whole OneShot catalog, compact: slug, title, one-liner, niche, price, and verification status per pack, plus the refund-policy summary once. Use this for an overview, then call get_pack on a specific slug for full detail. |
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 3 tools
Each tool has a clearly distinct purpose: search_packs finds by keyword, get_pack shows full detail for a specific slug, and list_packs provides a compact overview. There is no overlap or ambiguity between them.
All three tool names follow a consistent verb_noun pattern: search_packs, get_pack, list_packs. The naming is uniform and predictable.
Three tools is well-scoped for a read-only catalog browsing server. Each tool serves a distinct and necessary function without redundancy or excessive granularity.
The tool surface fully covers the domain of browsing and retrieving OneShot packs: search, overview, and full detail. There are no missing operations for a catalog of this type.