Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Checkpoints of the latest round

patroltech_rounds_get_checkpoints
Read-onlyIdempotent

Use when you want to know which checkpoints were scanned and which were missed in the latest round of a route. Returns the latest round of a route: the checkpoints scanned (with time, UTC) and the ones missing. Without route and several active routes it returns the routes to choose from. Do not use when you need the definition of routes or checkpoints.

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_rounds_get_checkpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeNoRoute name. Omit it (do not send it empty) if the user has not given one.
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

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description still earns credit by disclosing a non-obvious behavior: omitting `route` when multiple routes are active returns a route-selection list rather than an error, plus it states the return shape (scanned checkpoints with UTC time, missing checkpoints). It omits edge cases like what happens with zero active routes, which keeps it short of a 5.

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, all front-loaded: purpose and return content first, fallback behavior second, exclusions last. No restatement of the title and no filler.

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?

No output schema exists, and the description compensates by naming exactly what comes back (scanned checkpoints with UTC time, missing checkpoints, or a route list when ambiguous). With annotations covering safety and the schema covering both parameters, an agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so the baseline is 3 and the schema already explains omitting `route` and when to pass `organization`. The description adds value beyond the schema by describing the consequence of omitting `route` (a list of routes to choose from), which changes how the agent sequences the call rather than just what to pass.

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 specific verb and resource: returns the latest round of a route, with the checkpoints scanned (with time, UTC) and the ones missed. It also sets itself apart from definition-oriented tools with 'Do not use when you need the definition of routes or checkpoints', so an agent can pick it over patroltech_routes_get_schedules or patroltech_checkpoints_list without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('Use when you want to know which checkpoints were scanned and which were missed'), explicit when-not ('Do not use when you need the definition of routes or checkpoints'), and it spells out the fallback path when no route is supplied with several active routes. Nothing is left 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