Skip to main content
Glama

Make My QR Codes

Make a code

create_code

Save a new code in the account. "url" and "vcard" are changeable codes: they hold a short makemyqrcodes.com link, can be pointed somewhere new after printing, count scans, and use the account's allowance. The other types are static and always free. Links are screened before saving. Returns the code's id, link and a scan test; use download_code for the file.

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": {
      "type": "<type>"
    },
    "name": "create_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNotype "url": the web address the code opens, e.g. https://example.com/menu
nameNoShown in the account; made from the content if left out
ssidNotype "wifi": network name
textNotype "text": the message shown when scanned
typeYesurl (website link) and vcard (contact card) are changeable; wifi, text, email, phone and sms are static
designNoHow the code looks. All optional; dark squares on a light background scan best.
endingNoChangeable codes: a custom link ending (makemyqrcodes.com/<ending>). Random if left out. Can't be changed later.
folderNo
contactNotype "vcard": the contact card people save. Needs first, last or org.
email_toNotype "email": address the new email goes to
email_bodyNo
sms_messageNotype "sms": text the message starts with
wifi_hiddenNotype "wifi": the network is hidden
phone_numberNotypes "phone" and "sms": the number to call or text
email_subjectNo
wifi_passwordNotype "wifi": password (leave out when wifi_security is "nopass")
wifi_securityNotype "wifi": WPA covers WPA2 and WPA3. Default WPA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses that links are screened before saving, that changeable codes count scans and draw on the account allowance while static ones are free, and that it returns id, link and a scan test. That is substantive behavioral context a schema cannot carry.

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?

Four compact sentences with the core action front-loaded and the type economics in the middle. A little of the type split duplicates the schema enum text, but nothing is padded or buried.

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

Completeness4/5

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

For a 17-parameter nested create with no output schema, the description covers the return payload (id, link, scan test), validation screening and quota effects, while per-type field requirements are already in the schema. Only the make_static_code boundary and failure behavior are left unaddressed.

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

Parameters4/5

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

Schema coverage is 82%, so the baseline is 3, and the description adds the commercial semantics the schema lacks: changeable codes hold a makemyqrcodes.com link, can be re-pointed after printing, and consume the account allowance. The type distinction itself is partly restated from the enum description, keeping it just above baseline.

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 opens with a concrete verb+resource ("Save a new code in the account") and goes on to segment the resource by type, so an agent knows exactly what the tool produces. It never mentions the sibling make_static_code, so there is no explicit differentiation from the tool an agent might reach for the static types.

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

Usage Guidelines4/5

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

It clearly frames the changeable (url/vcard) vs static types and routes the file download to download_code, which is real when-to-use guidance. The notable gap is that make_static_code is never named, leaving ambiguity about whether static types belong here or in that sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources