Skip to main content
Glama

show-connect-qrcode

Generate a QR code from a connection URI to enable secure blockchain interactions through MetaMask without exposing private keys.

Instructions

Show the connect QR code for a given connect URI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesConnect URI

Implementation Reference

  • The execute handler for the 'show-connect-qrcode' tool. Generates a QR code Data URL from the input URI using the QRCode library and returns it as an image content response.
    execute: async (args) => {
      const uri = args.uri;
      const qrCode = await QRCode.toDataURL(uri, {
        width: 200,
      });
      return imageContent({
        url: qrCode,
      });
    },
  • Zod input schema defining the 'uri' parameter as a required string.
    parameters: z.object({
      uri: z.string().describe("Connect URI"),
    }),
  • The server.addTool call that registers the 'show-connect-qrcode' tool with FastMCP, including name, description, schema, and handler.
    server.addTool({
      name: "show-connect-qrcode",
      description: "Show the connect QR code for a given connect URI.",
      parameters: z.object({
        uri: z.string().describe("Connect URI"),
      }),
      execute: async (args) => {
        const uri = args.uri;
        const qrCode = await QRCode.toDataURL(uri, {
          width: 200,
        });
        return imageContent({
          url: qrCode,
        });
      },
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't explain how it behaves—for example, whether it displays the QR code visually, returns it as data, requires specific permissions, or has side effects. This leaves significant gaps in understanding the tool's operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely involves visual or data output (QR code). It doesn't explain what 'Show' entails—e.g., whether it returns an image, text, or triggers a display—or address potential complexities like error handling. This leaves the agent with insufficient context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the single parameter 'uri' documented as 'Connect URI'. The description adds no additional meaning beyond this, such as format examples or usage context. Since the schema handles the parameter documentation adequately, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Show') and the resource ('connect QR code for a given connect URI'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-connect-uri' or explain what a 'connect QR code' is used for in this context, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as how it relates to 'get-connect-uri' or other sibling tools. It lacks context about prerequisites, timing, or exclusions, leaving usage unclear beyond the basic action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xiawpohr/metamask-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server