Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Propose changing an alert

patroltech_alerts_propose_set_preference

Use when you want to turn on or off a notice the user receives. It only adds a proposal to the pending batch of this connection (up to 10 changes); nothing changes in the account yet. Show the returned summaries to the user and call patroltech_proposals_confirm only after they agree.

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": {
      "type": "<type>",
      "channel": "<channel>",
      "enable": "<enable>"
    },
    "name": "patroltech_alerts_propose_set_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesAlert type: pending_route, missed_route, upcoming_deadline, patroller_inactive (guard inactive), suspicious_scan, role_assignment, incident_created, incident_status_changed, incident_assigned or incident_comment.
enableYestrue = start receiving it on that channel; false = stop receiving it.
channelYesChannel: email, push or whatsapp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the key behavioral traits: this only appends to the connection's pending batch, that batch is capped at 10 changes, and nothing changes in the account yet. That is exactly the non-obvious information an agent needs before calling a staged-mutation tool.

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 tight sentences: trigger first, then the staging constraint, then the required follow-up step. No filler, and the most decision-relevant fact (nothing changes yet) is front-loaded after the trigger.

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 tells the agent to expect 'returned summaries' and what to do with them, and it covers the batch limit and the confirmation path. For a 3-parameter staging tool, an agent has everything needed to call it and handle the result correctly.

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 both enums (alert type, channel) plus the enable boolean are fully documented in the schema, so the description need not carry parameter meaning. The phrase 'turn on or off' loosely echoes the enable flag but adds no enum or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action (turn a notice on/off for the user) and immediately clarifies that it only stages a change rather than applying it. It is distinguishable from sibling proposal tools like patroltech_proposals_confirm and patroltech_proposals_cancel. However, it paraphrases the resource as 'a notice' rather than naming alert preferences, so the mapping to the tool name takes a small inference.

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?

It opens with an explicit trigger ('Use when you want to turn on or off a notice the user receives') and then prescribes the downstream flow: show the returned summaries to the user, and call patroltech_proposals_confirm only after they agree. That names the alternative action and its precondition, leaving nothing to inference.

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