Stock API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STOCK_API_KEY | Yes | API key for Stock API | |
| STOCK_API_COUNTRY | No | Country code for API | it |
| STOCK_API_BASE_URL | No | Base URL for Stock API | https://stock-api.dealerk.com |
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_vehiclesB | Discover vehicle inventory with comprehensive overview and sample listings. Shows total counts by make, fuel, condition plus representative vehicle examples with refinement suggestions. |
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 possible ambiguity or overlap. The tool's purpose is clear and singular.
The single tool name 'search_vehicles' follows a clean verb_noun convention. Consistency is not an issue with one tool.
A single tool feels thin for a server named 'Stock API MCP Server', but the tool itself is comprehensive in scope, providing search, counts, and refinements. It borders on acceptable but likely needs more tools for full coverage.
The server only offers search functionality. Missing essential operations like creating, updating, or deleting vehicle records, making the surface severely incomplete for a stock/inventory management domain.