PromptBin
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_promptsB | Search prompts by content, title, tags, or description |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_all_prompts | List all available prompts with metadata |
| flask_status |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The single tool's purpose is clearly distinct by default.
The sole tool uses a clear verb_noun pattern: search_prompts. This is consistent, predictable, and matches its function.
A single search-only tool feels far too thin for a server named PromptBin, which implies a prompt storage and management domain. Even a minimal prompt management server would need at least creation and listing capabilities.
The server exposes only search, with no way to add, update, delete, or retrieve prompts directly. This is severely incomplete for the apparent prompt-management scope and would cause agent failures for any non-search workflow.