Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Qrcode

create_qrcode

Generate a PNG QR code image from text or URL and save it to a specified path, with optional overwrite support.

Instructions

Generate a QR code image (PNG) from text or URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data": "<data>",
      "path": "<path>"
    },
    "name": "create_qrcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
pathYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the output format (PNG) and input type, but not that it writes a file to disk, what happens when the target path already exists, whether the default overwrite=false causes an error or silently skips, or whether directories are created. For a file-writing tool these are material gaps.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; every word earns its place. It is efficient rather than padded, though the terseness is part of why parameter and behavioral details are missing.

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?

An output schema exists, so return values need not be explained, but the tool writes a file whose destination and overwrite semantics are undocumented, and there are no annotations to fall back on. For a three-parameter file-producing tool with 0% schema coverage, the definition is not complete enough to invoke confidently.

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?

Schema description coverage is 0% across three parameters, so the description must compensate and mostly does not. "From text or URL" loosely explains the data parameter and "(PNG)" hints at the path extension, but path and overwrite are left entirely to bare type names in the schema.

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 gives a specific verb (Generate) and resource (QR code image) plus the output format (PNG) and accepted input (text or URL). The purpose is unmistakable and distinguishable from siblings like create_pdf or create_docx by resource, though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or constraints. An agent gets no signal about when a QR code is the right artifact versus, say, embedding a link in a document, and nothing about when overwrite should be set.

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

Deploy Server

Other Tools