Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Unreviewed checkpoints

patroltech_checkpoints_list_unreviewed
Read-onlyIdempotent

Use when you want to see which checkpoints have gone the longest without being scanned. Returns checkpoints from never scanned to longest without a scan, with lastScan (UTC) and daysWithoutScan. atLeast: true means the last scan is older than what could be read (say "more than N days"); noVisibleScans: true means no scan of it is visible (never scanned, or older than the data retention period). 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_unreviewed"
  }
}

Input Schema

NameRequiredDescriptionDefault
minDaysNoOnly the ones with at least this many days without a scan. Omit it to see all.
locationNoOnly the checkpoints of this location. Omit it for all.
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
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context beyond them: sort order (never scanned first), UTC timestamps, the meaning of `atLeast` ('more than N days') and `noVisibleScans` (including the data-retention caveat). This is exactly the output semantics an agent needs with no output schema present.

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?

Four compact sentences, front-loaded with the trigger and exclusion, then the flag semantics. Every sentence carries distinct information; 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?

For a read-only list tool with no output schema, the description supplies return ordering, the key returned fields, and the interpretation of ambiguous flags. Nothing needed to call or interpret the result is missing.

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 all three parameters (minDays, location, organization) are documented in the schema. The description adds no syntax or format detail beyond that, so the 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 ('see which checkpoints have gone the longest without being scanned') plus the return ordering, and explicitly distinguishes itself from the round-scoped sibling ('Do not use when you need the scans of one round'). An agent can separate it from checkpoints_list and rounds_get_checkpoints without opening schemas.

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?

Leads with the selecting condition ('Use when you want to see which checkpoints have gone the longest without being scanned') and adds an explicit exclusion pointing at the alternative use case. Both when-to-use and when-not-to-use are stated.

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