QR Branding

Build a geo: URI QR

qr_build_geo

Read-onlyIdempotent

Encode a latitude and longitude pair into a geo: URI QR code so scanning opens the location directly in the device's default maps app. Build scannable location codes from decimal degrees.

Instructions

Encode a latitude/longitude pair into a geo: URI QR. Scanning opens the location in the device's default maps app.

Input Schema

Name	Required	Description	Default
`latitude`	Yes	Latitude in decimal degrees (-90 to 90).
`longitude`	Yes	Longitude in decimal degrees (-180 to 180).

Output Schema

Name	Required	Description
`format`	Yes	File format the engine rendered: png, svg, jpg, webp or pdf.
`payload`	Yes	The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...).
`filePath`	No	PDF in the stdio package only: local temp file the PDF was written to.
`mimeType`	No	MIME type of the rendered file (the engine's contentType).
`sizeBytes`	No	Size of the rendered file in bytes, as reported by the engine.
`resourceUri`	No	PDF on the remote server only: URI of the embedded resource block that carries the file.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Oct 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: the produced QR resolves to a location opened in the device's default maps app, which tells the agent what the artifact is for.

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?

Two sentences, no filler, with the core action first and the downstream behavior second. Every clause earns its place.

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 two-parameter, fully documented, output-schema-backed tool with rich annotations, the description supplies what an agent needs to invoke it correctly. Only minor details (e.g., URI precision or format of the encoded string) are left unstated, and the output schema covers returns.

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% and both parameters carry ranges and units in the schema itself. The description only restates 'latitude/longitude pair', adding no format, precision, or edge-case meaning beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb (encode) and resource (a geo: URI QR) plus the two inputs, so the agent knows exactly what this produces. It is distinguishable from the qr_build_wifi and qr_build_vcard siblings by the geo domain, though no sibling is named explicitly and none needs to be.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for location QR codes, but there is no when-to-use/when-not-to-use guidance and no mention of alternatives such as qr_generate or qr_generate_from_template. Adequate but with a clear gap.

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

Deploy Server