Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Propose adding or removing a route checkpoint

patroltech_routes_propose_change_checkpoint

Use when you want to add or remove a checkpoint on a route. 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": {
      "route": "<route>",
      "checkpoint": "<checkpoint>",
      "operation": "<operation>"
    },
    "name": "patroltech_routes_propose_change_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesRoute name.
operationYesadd (at the end of the route) or remove.
checkpointYesCheckpoint name.
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.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds substantial context: the change only enters a pending batch of up to 10, nothing mutates in the account yet, and confirmation is a separate deliberate step. That is exactly the behavioral nuance an agent needs before calling a mutation.

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 short sentences, front-loaded with the trigger, followed by the batch constraint and the confirmation protocol. No redundant restatement of the title or 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?

No output schema exists, yet the description tells the agent what comes back ('the returned summaries') and what to do with it, closing the loop that would otherwise be missing. Combined with full schema coverage and annotations, nothing needed to call this correctly is absent.

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 route, checkpoint, operation and organization are already documented in the schema, including the 'add (at the end of the route)' semantics and the organization guidance. The description adds no parameter-level detail beyond what the schema provides, so the 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?

States a specific verb pair and resource: 'add or remove a checkpoint on a route.' That is precise enough to separate it from patroltech_checkpoints_propose_create (creates a checkpoint) and patroltech_routes_propose_add_time_window. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

Gives an explicit trigger ('Use when you want to add or remove a checkpoint on a route') plus a hard workflow rule: show returned summaries to the user and call patroltech_proposals_confirm only after they agree. The alternative path (proposals_confirm) and the condition that selects it are spelled out.

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