Drop Beacon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | Optional API key for authentication; if not set, the server runs without authentication. | |
| DATABASE_URL | Yes | Connection string for the Drop Beacon database (e.g., Neon PostgreSQL connection string). |
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 |
|---|---|
| search_productsB | Search currently available public EDC catalog listings. Prices may represent different configurations; verify the product page before comparing or purchasing. |
| get_latest_dropsA | Read in-stock listings first seen within seven days. First seen is a discovery date, not a manufacturer release date. Results are a bounded sample, not the entire market. |
| get_brand_infoB | Find a public brand profile and its available-product count. No internal analytics or customer records. |
| check_availabilityA | Find available catalog matches for a product name. No match does not mean unavailable everywhere. Confirm precise material, configuration, price and retailer stock on the linked page. |
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
Most tools have clearly distinct intents: get_latest_drops, get_brand_info, and check_availability are separable by purpose. However, search_products and check_availability both return available listings and could be confused, though their descriptions distinguish general search from a specific product-name availability check.
All tool names follow a consistent snake_case verb_noun pattern: search_products, get_latest_drops, get_brand_info, check_availability. The verbs vary appropriately with the action, and there is no mixing of conventions.
Four tools are well-scoped for a read-only EDC catalog discovery server. Each tool covers a distinct user need (search, new drops, brand info, availability check), with no bloat or excessive thinness.
The surface covers core discovery operations: searching products, viewing latest drops, getting brand info, and checking availability. Minor gaps include no direct product-detail endpoint or category/brand listing, though the descriptions point to external linked pages for detailed verification.