Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Checkpoint list

patroltech_checkpoints_list
Read-onlyIdempotent

Use when you need to know which checkpoints exist, in which location and with which identifier. Returns every checkpoint with its id (what the tools on specific checkpoints take, such as the QR sheet), its location and identifier (the 8-character code typed as manual code in the app). With truncated: true the list is capped: do not state totals or absences. Do not use when you need the scans of one round.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patroltech_checkpoints_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNoOmit unless the account has more than one organization; then the exact name (or id) as listed by patroltech_account_get_context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — that a `truncated: true` result caps the list and the agent must not state totals or absences — but that sentence is ambiguous since `truncated` appears nowhere in the input schema, making it unclear whether it is an input switch or an output flag. No pagination or ordering behavior is described.

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?

Front-loaded with the usage condition, then the return shape, then exclusions — a sensible order with no filler. The third sentence is slightly compressed to the point of ambiguity about what `truncated` refers to.

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?

With no output schema, the description carries the return-value burden and does it well: it names the fields and explains what `identifier` is for (the manual code typed in the app) and what `id` feeds (QR sheet tooling). Missing only the relationship to checkpoints_list_unreviewed and clarification of the truncated flag.

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?

There is exactly one parameter (`organization`) and the schema documents it at 100% coverage, including the multi-org precondition and a pointer to account_get_context. The description adds nothing about it, but with full schema coverage the baseline of 3 is appropriate.

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 and resource ('know which checkpoints exist') plus the exact fields returned (id, location, identifier), so an agent knows what it gets. It distinguishes itself from the rounds-scan sibling, but never contrasts with the near-identically named patroltech_checkpoints_list_unreviewed, which is the most likely confusion point.

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?

Opens with an explicit 'Use when' condition and adds a real exclusion: 'Do not use when you need the scans of one round,' which routes the agent to the rounds family. A deduction because the very similar sibling checkpoints_list_unreviewed is not addressed, leaving that selection to inference.

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