audited Aug 28, 2026in 10s
67/ 100

9 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use72
Usefulness89
Human experience22
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
generate_verified_qr: warning

generate_verified_qr

Generate a static QR asset, structurally review its payload, assess quiet zone and contrast settings, decode the final SVG, PNG, JPG, or WebP file, compare payload hashes, and return an evidence-linked receipt. Asset bytes are returned only when final-file decoding matches the requested payload.Answers a question. Declared read only.
pagehttps://qrcodecrafter.com/
implementation
viaimperative
entry pointdocument
registered after1786ms
executepresent
api surface
valuerequired
formatoptional
contentTypeoptional
sizeoptional
marginoptional
fgColoroptional
bgColoroptional
errorCorrectionLeveloptional
logooptional
annotations
read onlytrue
destructivefalse
idempotenttrue
open worldnot declared
untrusted contenttrue
titlenot declared
2 findings
warningAnnotation mismatch
2.1 / 3
2 tools declare readOnlyHint: true although the name says the call writes (generate_verified_qr).
generate_verified_qr: readOnlyHint=true; generate_bulk_qr: readOnlyHint=true
fix
// Set destructiveHint/idempotentHint to match what this tool actually does.
{ name: "generate_verified_qr", annotations: { destructiveHint: true } }
warningHuman parity
1.8 / 8
7 of 9 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
generate_verified_qr, generate_bulk_qr, create_dynamic_qr, manage_dynamic_qr, create_dynamic_qr_campaign
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="generate_verified_qr" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "generate_verified_qr",
  "description": "Generate a static QR asset, structurally review its payload, assess quiet zone and contrast settings, decode the final SVG, PNG, JPG, or WebP file, compare payload hashes, and return an evidence-linked receipt. Asset bytes are returned only when final-file decoding matches the requested payload.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "value": {
        "type": "string",
        "minLength": 1,
        "maxLength": 2048,
        "description": "Exact QR payload to encode, such as an HTTPS URL, WIFI payload, vCard, calendar event, payment URI, or text."
      },
      "format": {
        "type": "string",
        "enum": [
          "svg",
          "png",
          "jpg",
          "webp"
        ],
        "default": "png",
        "description": "Output format to generate and decode. Verification supports SVG, PNG, JPG, and WebP."
      },
      "contentType": {
        "type": "string",
        "enum": [
          "url",
          "appstore",
          "social",
          "text",
          "wifi",
          "email",
          "sms",
          "phone",
          "whatsapp",
          "vcard",
          "event",
          "location",
          "crypto",
          "pix",
          "upi",
          "phonepe",
          "swish",
          "sepa",
          "ideal",
          "mobilepayvipps",
          "qris",
          "paypal",
          "venmo",
          "cashapp",
          "promptpay",
          "vietqr",
          "swissqr"
        ],
        "description": "Optional hint describing the QR payload type. This does not change generation behavior but helps agents choose examples and validation."
      },
      "size": {
        "type": "integer",
        "minimum": 256,
        "maximum": 4096,
        "default": 1024,
        "description": "Requested output size in pixels for raster/SVG output or points for PDF/EPS."
      },
      "margin": {
        "type": "integer",
        "minimum": 0,
        "maximum": 16,
        "default": 4,
        "description": "Quiet-zone margin around the QR code."
      },
      "fgColor": {
        "type": "string",
        "pattern": "^#[0-9a-fA-F]{6}$",
        "default": "#000000",
        "description": "Foreground color as a six-digit hex value."
      },
      "bgColor": {
        "type": "string",
        "pattern": "^#[0-9a-fA-F]{6}$",
        "default": "#ffffff",
        "description": "Background color as a six-digit hex value."
      },
      "errorCorrectionLevel": {
        "type": "string",
        "enum": [
          "L",
          "M",
          "Q",
          "H"
        ],
        "default": "H",
        "description": "QR error correction level. Use H when embedding logos."
      },
      "logo": {
        "type": "string",
        "maxLength": 1398230,
        "pattern": "^data:image\\/(png|jpe?g|webp);base64,[A-Za-z0-9+/]+={0,2}$",
        "description": "Optional PNG, JPG, or WebP data URL for a centered logo. Keep source files under 1MB."
      }
    },
    "required": [
      "value"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "untrustedContentHint": true
  }
}
Showing generate_verified_qr

Findings

WebMCP use

72 / 100 · weight 50
passTools registered
4 / 4
7 imperative tools and 2 declarative forms registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither. The 2 declarative form tools on the page stay usable regardless.
warningRegistration timing
2 / 4
The slowest tool took 1786.6850001811981ms to register, past the 1000ms an agent reading the registry at first paint would wait for. 2 further tools carried no measurable registration time.
toolmanage_qr_vault
manage_qr_vault: registered at 1786.6850001811981ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
passCanonical entry point
4 / 4
All 7 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 7 tools declare a structurally valid object input schema.
warningSchema quality
3.1 / 4
2 of 9 tool schemas are harder for an agent to use than they need to be: create_qr_vault 1 parameter has no description (name).
toolcreate_qr_vault
create_qr_vault: 1 parameter has no description (name); manage_qr_vault: 9 parameters have no description (action, vaultId, managementToken, name)
fix
{
  name: "create_qr_vault",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 7 tools declare an execute handler.
passAnnotations present
4 / 4
All 7 tools declare a readOnlyHint, so an agent knows which calls change state.
warningAnnotation mismatch
2.1 / 3
2 tools declare readOnlyHint: true although the name says the call writes (generate_verified_qr).
toolgenerate_verified_qr
generate_verified_qr: readOnlyHint=true; generate_bulk_qr: readOnlyHint=true
fix
// Set destructiveHint/idempotentHint to match what this tool actually does.
{ name: "generate_verified_qr", annotations: { destructiveHint: true } }
not applicableUntrusted content hint
0 / 2
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
7 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

89 / 100 · weight 30
warningNaming quality
1.8 / 2
Tool naming makes selection harder than it needs to be: 2 names do not start with a verb (manage_dynamic_qr).
toolmanage_dynamic_qr
fix
{ name: "manage_dynamic_qr" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
not applicableCoverage vs. site type
0 / 8
This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

22 / 100 · weight 20
warningHuman parity
1.8 / 8
7 of 9 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolgenerate_verified_qr
generate_verified_qr, generate_bulk_qr, create_dynamic_qr, manage_dynamic_qr, create_dynamic_qr_campaign
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="generate_verified_qr" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
9
run time
10s
finished
Aug 28, 2026