Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Rounds status

patroltech_rounds_get_status
Read-onlyIdempotent

Use when you want to know how many rounds are in progress, completed or incomplete. Returns the number of rounds by status (open = in progress, completed, incomplete = incomplete or expired) over the last windowDays days. 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_status"
  }
}

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 readOnly, idempotent and non-destructive, so safety is covered. The description adds genuine behavioral content beyond that: results are aggregated counts by status over a time window, and what 'incomplete' actually means (incomplete or expired). It does not describe pagination or ordering, but for an aggregate tool that is minor.

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, front-loaded with the trigger, then the return shape, then the exclusion. No filler and nothing repeated from annotations or schema.

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 no output schema, the description correctly explains the return value (counts per status) and defines the status vocabulary, which is exactly what an agent needs. The dangling `windowDays` reference is the one unresolved gap for a tool this simple.

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% for the single `organization` parameter, so the baseline is 3. However, the description references a `windowDays` argument that does not exist in the input schema, which is a real inconsistency an agent could trip over; it also adds no guidance on `organization` beyond what the schema says.

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 rounds) and enumerates the exact statuses returned, with parenthetical definitions for each. An agent can distinguish it from rounds_list_by_route or rounds_get_round 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?

Opens with an explicit 'Use when you want to know how many rounds...' trigger and adds a negative 'Do not use when you need the definition of routes or checkpoints'. It stops short of naming the specific sibling to use instead for route/checkpoint data, but the context is clear.

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