Conecto

Make a QR code

qr_create

A QR code for a link or any text (a payment link, a booking page, Wi-Fi details), saved in the file store as PNG or SVG with a download link. Dark modules must contrast with the background so phones can read it. Costs $0.01 per call; nothing if it fails.

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

Input Schema

Name	Required	Description	Default
`dark`	No		#171717
`data`	Yes
`name`	No	File name; defaults to "QR code".
`size`	No	PNG width and height in pixels.
`light`	No		#ffffff
`format`	No		png
`error_correction`	No	Higher survives damage or a logo on top, at the cost of density.	medium

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only supply the generic safety flags (readOnly=false, destructive=false, idempotent=false). The description adds information annotations cannot: the artifact is persisted to the file store, a download link is produced, the call costs $0.01 and is free on failure, and dark modules must contrast with the background for scannability.

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?

Three sentences, each earning its place: what it produces, the contrast constraint that prevents unusable output, and the pricing. The core capability is front-loaded with no filler.

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 7-param creation tool with no output schema, the description covers output artifact, storage location, download link, and cost. A minor gap: it does not say how to retrieve the file later (e.g. files_list) or explain the error_correction trade-off beyond what the schema already says.

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?

With only 43% schema coverage, four parameters (dark, data, light, format) rely on the description, and it compensates for most of them: format is spelled out as PNG/SVG, data as 'a link or any text', and the dark/light contrast rule gives meaning to the two color hex params. It adds nothing for size beyond the schema's own bounds, but the compensation is substantial.

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?

The description states a concrete resource (a QR code from a link or text) and the side effect (saved in the file store as PNG/SVG with a download link). No sibling tool does anything similar, so differentiation is trivially satisfied and the agent knows exactly what it gets.

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?

The parenthetical examples (payment link, booking page, Wi-Fi details) give clear intended-use context, which is stronger than most definitions. There are no stated exclusions or alternatives, but none are needed here since this is the only QR tool in the sibling set.

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

All Conecto 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?