Recash1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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 |
|---|---|
| searchC | This will filter what you want from the products on the data base |
| all_productsA | This will gives you all the products with codes on the data base |
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 2 tools
The two tools have clearly distinct purposes: all_products retrieves all products, and search filters them. There is no overlap.
The naming mixes different styles: all_products uses snake_case with a noun, while search is a single verb. While both are recognizable, the lack of a consistent verb_noun pattern reduces clarity.
With only 2 tools, the server feels minimal for a product database. Typical CRUD operations are missing, making the tool set too thin for robust interaction.
The tools only support read operations (list all and search). There are no create, update, or delete tools, which are essential for complete product management. This is a significant gap.