QRCode_MCP
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 |
|---|---|
| qrcodeB | Generate a QR code image |
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 confusion or overlap between tools. The single tool 'qrcode' has a clear and distinct purpose of generating QR code images, making disambiguation trivial.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'qrcode' follows a simple, descriptive pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for most practical server purposes, as it limits functionality and flexibility. While it might suffice for a minimal QR code generator, typical servers benefit from multiple tools to handle related operations, such as decoding or customizing QR codes.
The tool surface is severely incomplete for a QR code domain. It only provides generation, missing essential operations like decoding QR codes, customizing appearance, or handling different formats, which are common in such tools and could lead to agent failures in broader tasks.