Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Account summary

patroltech_account_get_summary
Read-onlyIdempotent

Use when you want an overview of the account: rounds, guards and incidents. Returns the rounds of the last 7 days by status, the number of guards by status (active, inactive, in alert), the total of checkpoints and the suspicious scans detected. Do not use when you need a detailed list; the specific tools give it.

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

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond them: the rounds window is scoped to the last 7 days and the payload is aggregate counts by status. It does not state whether 'suspicious scans' or the guard counts use the same window, which is the one transparency gap.

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: purpose first, payoff (what comes back) second, exclusion third. No filler and nothing is buried.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so concretely (rounds by status, guards by status, checkpoint total, suspicious scans). Minor ambiguity about the time window for the non-round metrics is the only shortfall.

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 coverage is 100% and the single 'organization' parameter is fully documented in the schema, including its 'omit unless multi-org' rule and the reference to patroltech_account_get_context. The description adds nothing about it, so baseline 3 is correct.

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?

The description names a specific verb+resource ('overview of the account') and enumerates the exact content domains (rounds, guards, incidents, checkpoints, suspicious scans). An agent can distinguish it from the granular siblings (rounds_list_by_route, patrollers_get_stats) 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?

It gives both a when ('you want an overview of the account') and an explicit when-not ('Do not use when you need a detailed list'), which is stronger than most. The gap is that the alternatives are referred to only generically as 'the specific tools' rather than naming the sibling that should be used instead.

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