Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Incident detail

patroltech_incidents_get
Read-onlyIdempotent

Use when you want an incident in detail: description, comments and who is handling it. Returns one incident: description, status, priority, category, reporter, assignee, linked checkpoints, history of comments and status changes (author and UTC date) and the number of photos and videos (they can only be seen in the dashboard). One older than the data retention period comes with hidden: true and no details. Do not use when you need scans or rounds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "incident": "<incident>"
    },
    "name": "patroltech_incidents_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
incidentYesTitle (or part of it), `id` or number in the incident list (without status filter).
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.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the exact payload shape, the constraint that photos and videos are counted but only viewable in the dashboard, and the retention edge case where old incidents return `hidden: true` with no details. The retention behavior is exactly the kind of non-obvious trait that prevents misinterpretation of an empty result.

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 usage trigger, then the return contents, then the exclusion — a sensible order with no filler. The field enumeration in the middle sentence is long but justified since there is no output schema.

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 carries the full burden of describing return values and does so thoroughly, including media limitations and the retention/hidden case. Nothing an agent needs in order to call and interpret this tool 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 the meaning of `incident` (title fragment, id, or list number) and the `organization` omission rule are already fully documented. The description adds no parameter-level guidance 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 ('get an incident in detail') and immediately enumerates what makes it a detail view (description, comments, assignee). An agent can distinguish it from patroltech_incidents_list (list) and the rounds/scans tools without opening the 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?

Explicit trigger ('Use when you want an incident in detail') plus an exclusion ('Do not use when you need scans or rounds'). The exclusion targets fairly distant resources rather than naming the closer sibling patroltech_incidents_list as the list alternative, so routing to the list tool is only implied.

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