Cocktail By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication with the Cocktail By Api Ninjas API |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1cocktailC | API Ninjas Cocktail API endpoint. Either name or ingredients parameter must be set. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as accessing the Cocktail API with specific parameter requirements.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.
One tool is too few for a server named 'Cocktail By Api Ninjas', which suggests a domain with multiple potential operations (e.g., search by name, ingredient, category, random cocktail). This minimal surface will likely cause agent failures due to limited functionality.
The server is severely incomplete for its apparent cocktail domain. It only offers a single generic endpoint without clear CRUD or lifecycle coverage (e.g., no distinct tools for searching, filtering, or retrieving detailed cocktail information), leaving significant gaps in functionality.