Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Round detail

patroltech_rounds_get_round
Read-onlyIdempotent

Use when you want the detail of a specific round of a route, scan by scan. Returns one round: status, guard, start and end, checkpoints done (with time) and pending; all times are UTC. Without date it is the latest round; other rounds of that day come in otherNearbyRounds. 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_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay of the round in the calendar of the account, YYYY-MM-DD. Omit it for the latest round.
timeNoApproximate start time, HH:mm in the local time of the account. Only together with `date`.
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.1/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description only needs to add behavior — and it does: it discloses the default resolution (no `date` → latest round), the side field `otherNearbyRounds`, and that all times are UTC. It stops short of describing pagination or the size/shape of the checkpoint lists, which keeps it at 4.

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 'Use when' clause, then the return contents and defaults, then the exclusion — a sensible order with no filler. It loses a point for restating the 'without date → latest round' rule that the schema already gives verbatim.

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 four optional parameters and no output schema, the description correctly compensates by enumerating the returned fields and the UTC convention, which is exactly what the missing output schema would have supplied. The structure of `otherNearbyRounds` and the checkpoint list shapes remain undisclosed, a minor gap for a read-only 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%, including the YYYY-MM-DD and HH:mm patterns and the 'time only with date' constraint, so the schema carries the parameter burden. The description adds only the UTC time convention and re-states the default-latest behavior already documented on `date`; baseline 3 applies.

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 — the detail of a specific round of a route, scan by scan — and enumerates what comes back (status, guard, start/end, done vs pending checkpoints). This is clearly distinguishable from patroltech_rounds_list_by_route, rounds_get_status and rounds_get_checkpoints without opening any schema.

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?

Gives an explicit 'Use when' condition (wanting one round's detail, checkpoint by checkpoint) and an explicit 'Do not use when' exclusion (route or checkpoint *definitions*). The exclusion points at the routes/checkpoints tools rather than the closer siblings rounds_get_status and rounds_list_by_route, so the routing among round tools is left partly 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