Skip to main content
Glama
Sign In

QRdx

by io.github.bucharitesh
OverviewDiscussionsAdmin

Save a design as a theme

save_template

Save a design to QRdx as a saved theme, listed under Themes in the dashboard and offered in the editor. Needs a QRdx API key with full access on this MCP connection (Authorization: Bearer qrdx_…). It saves to the key's workspace: your own themes, or a team's shared themes (owners and admins, on plans with team themes). Counts against the plan's saved-theme limit (10 on Free). Pass design_qr's qrdxStyle as style.

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>",
      "style": "<style>"
    },
    "name": "save_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe theme's name, up to 50 characters
styleYesThe design: the qrdxStyle that design_qr returns (logoIcon and logoFileId included)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing auth requirements (full-access API key), workspace scoping (personal vs team shared, owners/admins, plan-gated), and a quota limit (10 on Free). These are exactly the operationally decisive facts an agent needs before a non-idempotent write.

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?

Dense but front-loaded: the purpose and outcome come first, followed by prerequisites and constraints. Four sentences all carry information, though the auth/workspace/quota clauses are packed tightly and could be trimmed slightly.

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?

No output schema exists, but the description explains the effect (theme appears in dashboard and editor) rather than a return value. Auth, scoping, and quota are covered; only the concrete response (e.g., a theme identifier) is unstated, which is a minor gap for a save operation.

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 100%, so the baseline is 3, but the description adds real meaning by tying 'style' to design_qr's qrdxStyle output, clarifying the expected value's origin beyond the schema's structural description.

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 ('Save a design ... as a saved theme') plus the observable outcome ('listed under Themes in the dashboard and offered in the editor'). This clearly separates it from generation siblings like design_qr and generate_qr_code.

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?

Gives a concrete usage directive ('Pass design_qr's qrdxStyle as style'), effectively specifying the upstream workflow that leads to this call. It stops short of explicit alternatives or when-not-to-use guidance, but the context is clear enough to route the agent.

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

All QRdx toolsInspect
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