Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Scans per guard

patroltech_scans_count_by_patroller
Read-onlyIdempotent

Use when you want how many scans each guard made over a period. Returns how many scans each guard made in the period (default: the last 7 days; dates are calendar days in the time zone of the account) and how many of them were valid, suspicious, invalid (rejected) and pendingReview, ordered by total (position), including guards without scans. Valid and suspicious are independent: a scan can be both. Scans older than the data retention period come without their guard and are counted together under "(sin vigilante)". With truncated: true only the most recent scans were counted: the counts are partial. Activity counts, not an assessment of the people. Do not use when round totals are enough.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date of the range (inclusive), YYYY-MM-DD.
fromNoStart date of the range, YYYY-MM-DD (never words like "yesterday").
periodNoRelative period. Use it when the user says "today", "yesterday", "last week", "last month" or similar. Omit it (and from/to) for the last 7 days.
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.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses the default window and account-timezone day boundaries, that `valid` and `suspicious` can overlap, that retained-out scans collapse into a '(sin vigilante)' bucket, and that `truncated: true` means partial counts. These are exactly the behavioral caveats an agent needs to interpret results without misleading the user.

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 trigger and the return shape, and every later sentence (status overlap, retention bucket, truncation) carries distinct information. Minor redundancy between the first two sentences, which both restate 'how many scans each guard made over a period'.

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 still enumerates the returned status buckets, the `position` ordering and the `truncated` flag, plus the retention edge case. Nothing essential for correct invocation or interpretation is missing for a 4-parameter, read-only aggregation tool.

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 coverage is already 100%, so the baseline is 3; the description adds real value by stating that omitting `from`/`to`/`period` yields the last 7 days and that dates are calendar days in the account time zone. It does not clarify the `organization` parameter beyond what the schema says, but the timezone/default semantics are a meaningful supplement.

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 (count scans per guard) plus the exact returned breakdown by status, ordering (`position`), and inclusion of guards without scans. An agent can immediately tell this apart from a raw scan listing like `scans_list_recent` because the output shape is spelled out.

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 trigger ('Use when you want how many scans each guard made over a period') and closes with an explicit exclusion ('Do not use when round totals are enough'). It does not name the concrete sibling to use instead, so the exclusion is directional rather than fully resolved.

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