Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Get the QR sheet of a location

patroltech_locations_get_qr_sheet

Creates a temporary link (valid for about one hour) to a printable PDF with the QR codes of a location's checkpoints; it changes nothing in the account. It returns when the link expires both in UTC (expiresAt) and in the local time of the account (expiresAtLocal, with its offset): tell the user the local one. Use this when the user wants to print or download the QR codes of a location, or of some of its checkpoints.

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": {
      "locationId": "<locationId>"
    },
    "name": "patroltech_locations_get_qr_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesId of the location, as listed by patroltech_account_get_context.
organizationNoOmit unless the account has more than one organization; then the exact name (or id) as listed by patroltech_account_get_context.
checkpointIdsNoOmit to print every QR checkpoint of the location; otherwise the ids to print.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond annotations: the link's ~1-hour validity, that it produces a PDF artifact, that it changes nothing in the account, and the shape of the returned expiry fields. 'Changes nothing in the account' sits in mild tension with readOnlyHint=false, but is consistent with a tool that mints an ephemeral link token rather than mutating data, and destructiveHint=false is reinforced.

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 tight sentences: what it returns, how long it lasts, and when to use it. The critical operational instruction ('tell the user the local one') is included without padding, and every clause carries information an agent needs.

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 compensates by naming the return fields (expiresAt, expiresAtLocal with offset) and instructing which to surface to the user. It also covers the TTL and side-effect profile, leaving nothing essential to inference for a 3-parameter read-ish 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 description coverage is 100%, so locationId, organization, and checkpointIds are already fully documented, including the cross-reference to patroltech_account_get_context. The description only restates the checkpoint-subset behavior ('or of some of its checkpoints'), adding little the schema doesn't already supply.

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 precise verb and resource: creates a temporary link to a printable PDF of a location's checkpoint QR codes. This is unmistakably distinct from siblings like patroltech_checkpoints_list or patroltech_locations_propose_edit, and the 'temporary link' framing prevents confusing it with a direct PDF download.

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 names the triggering intent: 'Use this when the user wants to print or download the QR codes of a location, or of some of its checkpoints.' It doesn't state when NOT to use it (e.g., to merely inspect checkpoint metadata, use checkpoints_list), but the positive routing is clear enough for correct selection.

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

All PatrolTech 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