Foundaree

Make a free QR code

create_qr_code

Make a free dynamic QR code on Foundaree for the signed-in user. The QR holds a fixed Foundaree link (foundaree.com/r/...), so the user can change where it goes later without printing it again. Use it when the user wants a QR code for a menu, shop, flyer, card, event or any link. Returns the QR image (show it to the user), the scan link inside the QR, and a page where they can download it as PNG or SVG for printing. Scanning needs no app or account. Needs the user to have connected their Foundaree account.

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": {
      "name": "<name>",
      "link": "<link>"
    },
    "name": "create_qr_code"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes	Where the QR should open: a full web address (https://...). Only http and https links work.
`name`	Yes	A short name only the user sees, e.g. "Cafe menu".

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only establish write / not-idempotent / not-destructive, and the description goes well beyond that: the account-connection prerequisite, the redirect model, and the return contents (QR image, scan URL, download page for PNG/SVG) with a clear instruction to show the image. It does not say whether calling twice creates duplicate codes or whether there are creation limits, which matters given idempotentHint=false.

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?

Purpose is front-loaded in the first sentence, followed by the mechanism, the when-to-use list, the returns, and the prerequisite. Every sentence carries distinct information an agent needs; nothing is repeated from the title or schema.

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

Completeness5/5

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

With no output schema, the description correctly covers the return values and even what the caller should do with the image. Auth prerequisite and the scanning experience (no app or account needed) round out what an agent needs for a two-parameter write tool.

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?

Schema coverage is 100%, so both parameters are already documented with examples and http/https constraints; the description adds no syntax or format guidance. The one meaningful contribution is clarifying that the QR encodes a redirect link rather than the raw target, but that is a partial explanation and sits in slight tension with the schema's 'Where the QR should open' wording.

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

Purpose5/5

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

States a specific verb and resource ('Make a free dynamic QR code') plus the mechanism (fixed Foundaree redirect link at foundaree.com/r/...). That 'dynamic' detail cleanly separates it from sibling tools like update_qr_code, delete_qr_code, and my_qr_codes.

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?

Explicitly says when to use it with concrete examples (menu, shop, flyer, card, event, any link). It notes the destination can be changed later but never names update_qr_code as the tool that does that, so a natural hand-off to a sibling is left implicit.

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

All Foundaree tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?