colacloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COLA_API_KEY | Yes | Your COLA Cloud API key, obtained from app.colacloud.us |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_colasA | Search and filter COLA (Certificate of Label Approval) records. COLAs are federal approvals for alcohol product labels in the US. Each record includes brand name, product details, label images, and enriched data like barcodes and AI-extracted features. Args: q: Full-text search query (searches brand, product name, origin) product_type: Filter by type - "malt beverage", "wine", or "distilled spirits" origin: Filter by country or US state (e.g., "california", "france") brand_name: Filter by brand name (partial match, case-insensitive) approval_date_from: Minimum approval date (YYYY-MM-DD) approval_date_to: Maximum approval date (YYYY-MM-DD) abv_min: Minimum alcohol by volume percentage abv_max: Maximum alcohol by volume percentage page: Page number for pagination (default: 1) per_page: Results per page (default: 20, max: 100) Returns: Search results with COLA summaries and pagination info |
| get_colaA | Get detailed information about a specific COLA by its TTB ID. Returns the full record including all label images, extracted barcodes, and AI-enriched fields like product descriptions, tasting notes, and category classifications. Args: ttb_id: The TTB (Alcohol and Tobacco Tax and Trade Bureau) ID, e.g., "23001001000001" Returns: Complete COLA record with images, barcodes, and enrichment data |
| search_permitteesA | Search permit holders (companies authorized to produce/import alcohol). Permittees are businesses that hold federal permits to manufacture, import, or wholesale alcohol products. Each permittee can have many COLAs. Args: q: Search by company name (partial match) state: Filter by US state (two-letter code, e.g., "CA", "NY") is_active: Filter by active permit status (true/false) page: Page number for pagination (default: 1) per_page: Results per page (default: 20, max: 100) Returns: Search results with permittee summaries and pagination info |
| get_permitteeB | Get detailed information about a permit holder. Returns the permittee's company details and their 10 most recent COLAs. Args: permit_number: The federal permit number, e.g., "NY-I-123" Returns: Permittee details with recent COLA summaries |
| lookup_barcodeA | Find COLAs by product barcode (UPC, EAN, etc.). Barcodes are extracted from label images using computer vision. This tool finds all COLAs that contain a specific barcode, useful for identifying products or tracking label changes over time. Args: barcode_value: The barcode number (UPC, EAN, etc.), e.g., "012345678905" Returns: Barcode info and all associated COLAs |
| get_api_usageA | Check your COLA Cloud API usage and rate limits. Returns current usage statistics including requests used this month, remaining quota, and rate limit information. Returns: Usage stats including tier, limits, and current period usage |
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 6 tools
Each tool has a clearly distinct purpose targeting different resources and actions within the COLA domain. get_cola retrieves specific records by TTB ID, search_colas performs filtered searches, lookup_barcode finds records by barcode, get_permittee retrieves permit holder details, search_permittees searches permit holders, and get_api_usage checks system usage - there is no functional overlap between these operations.
All tools follow a consistent verb_noun naming pattern (get_api_usage, get_cola, get_permittee, lookup_barcode, search_colas, search_permittees). The verbs 'get', 'lookup', and 'search' are appropriately differentiated based on the operation type, creating a predictable and readable naming convention throughout the set.
With 6 tools, this server is well-scoped for its COLA database domain. The count provides comprehensive coverage without bloat - each tool serves a distinct, necessary function for interacting with COLA records, permit holders, and system usage, making the set appropriately sized for the server's purpose.
The tool set provides excellent coverage for querying and retrieving COLA and permittee data, including search, lookup by various identifiers, and system monitoring. The only minor gap is the absence of write/update operations, but given the domain appears to be a regulatory database (likely read-only), the surface is appropriately complete for typical agent workflows.