MatMCP
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 |
|---|---|
| list_recipesB | List available recipes |
| get_recipe_by_indexC | Get a recipe by index from the list |
| search_mathem_ingredientsB | Search for ingredients on Mathem.se grocery store |
| add_to_mathem_basketC | Add a product to the Mathem.se shopping basket |
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 4 tools
The tools have mostly distinct purposes: list_recipes and get_recipe_by_index handle recipe browsing, while add_to_mathem_basket and search_mathem_ingredients focus on shopping basket and ingredient search. However, there is a slight overlap in the recipe domain where list_recipes and get_recipe_by_index could be confused if an agent needs to retrieve a specific recipe, but the descriptions clarify their distinct roles.
The naming is mixed with some consistency: list_recipes and get_recipe_by_index follow a verb_noun pattern, but add_to_mathem_basket uses a prepositional phrase and search_mathem_ingredients includes the domain name. This creates a readable but inconsistent convention across the tool set, with deviations from a uniform pattern.
With 4 tools, the count is reasonable for a server focused on recipes and grocery shopping. It covers key operations like listing, retrieving, searching, and adding items, making it well-scoped for its apparent purpose, though it could potentially benefit from additional tools for a more complete workflow.
The tool set covers basic recipe browsing and ingredient shopping, but there are notable gaps. For example, there is no tool to manage the shopping basket beyond adding items (e.g., remove or view items), and no update or delete operations for recipes. This limits the agent's ability to handle full lifecycle tasks in the domain.