Skip to main content
Glama

show-connect-qrcode

Generate a QR code to connect MetaMask wallets securely for blockchain interactions without exposing private keys, enabling simplified user onboarding.

Instructions

Show the connect QR code for a given connect URI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYes

Implementation Reference

  • Handler function that takes a URI, generates a QR code data URL using qrcode.toDataURL, and returns it as image content via imageContent.
    execute: async (args) => {
      const uri = args.uri;
      const qrCode = await QRCode.toDataURL(uri);
      return imageContent({
        url: qrCode,
      })
    },
  • Zod schema defining the input parameter 'uri' as a string.
    parameters: z.object({
      uri: z.string(),
    }),
  • Registration of the 'show-connect-qrcode' tool with FastMCP server.addTool, including name, description, parameters, and execute handler.
    server.addTool({
      name: "show-connect-qrcode",
      description: "Show the connect QR code for a given connect URI",
      parameters: z.object({
        uri: z.string(),
      }),
      execute: async (args) => {
        const uri = args.uri;
        const qrCode = await QRCode.toDataURL(uri);
        return imageContent({
          url: qrCode,
        })
      },
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'shows' a QR code, implying a read-only or display operation, but doesn't specify if this requires authentication, involves side effects (e.g., generating a new code), or details the output format (e.g., image data, URL). This leaves significant gaps for an agent to understand how to invoke it effectively.

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, efficient sentence with no wasted words, making it easy to parse. It front-loads the key action and resource, though it could benefit from more detail given the context.

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 complexity (a tool that likely generates or retrieves a QR code for blockchain connectivity), no annotations, no output schema, and low parameter coverage, the description is incomplete. It fails to explain what the tool returns (e.g., an image, a link), how it behaves, or how it fits with sibling tools, leaving the agent with inadequate information for reliable use.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description mentions 'for a given connect URI', which adds minimal meaning by indicating the parameter is a URI, but doesn't explain what a 'connect URI' is, its format, or where to obtain it. This insufficiently compensates for the low schema coverage.

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 differentiate from sibling tools like 'get-connect-uri' or explain what a 'connect QR code' specifically is, preventing 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 like 'get-connect-uri' or other blockchain-related tools in the sibling list. It lacks context about prerequisites, such as needing a valid URI from another source, or exclusions.

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/mcpilot'

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