Waferlock Robot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_URL | Yes | The API URL for the Waferlock Robot MCP service | |
| API_TOKEN | Yes | Your API token for authentication | |
| MCP_TOKEN | No | Optional token required for client connections | |
| SERVER_NAME | No | Override the MCP server name | |
| SERVER_VERSION | No | Override the server version |
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_manualsB | List all uploaded Waferlock product manuals |
| get_manual_infoB | Get information about a specific manual by ID |
| search_manualsC | Search for manuals by filename |
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 3 tools
Each tool has a clearly distinct purpose: get_manual_info retrieves details for a specific manual, list_manuals shows all manuals, and search_manuals finds manuals by filename. There is no overlap or ambiguity in their functions.
All tools follow a consistent verb_noun pattern (get_manual_info, list_manuals, search_manuals) with clear, descriptive names. There are no deviations in naming conventions.
With only 3 tools, the set feels thin for a product manual management system. While the tools cover basic retrieval and listing, it lacks operations like upload, update, or delete, which are typical for such a domain.
The tool set is significantly incomplete for managing Waferlock product manuals. It only supports read operations (get, list, search), missing essential CRUD functions such as create/upload, update, and delete, which are necessary for full lifecycle coverage.