Products API MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsC | Get a list of products with optional filtering and pagination. |
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 single tool has a clear and distinct purpose of retrieving products with filtering and pagination capabilities.
The single tool name 'get_products' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and predictable.
A server named 'Products API MCP Server' suggests a domain requiring CRUD operations, but it only provides a single 'get' tool. This is too few for the apparent scope, as it lacks create, update, delete, or other product-related operations, making it severely under-scoped.
The tool set is severely incomplete for a products API domain. It only supports retrieving products, with no coverage for creating, updating, deleting, or managing other aspects like categories or inventory. This will cause significant agent failures in typical product management workflows.