PatrolTech

Propose adding a route schedule

patroltech_routes_propose_add_time_window

Use when you want to add a schedule to 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>",
      "days": "<days>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "patroltech_routes_propose_add_time_window"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	End time, HH:mm local. If it is earlier than `from`, it ends the next day (20:00-05:00).
`days`	Yes	Days on which the time window STARTS.
`from`	Yes	Start time, HH:mm in the local time of the account.
`route`	Yes	Route name.
`organization`	No	Omit 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.

First observedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Despite annotations declaring readOnlyHint=false and destructiveHint=false, the description adds the crucial nuance: nothing changes in the account yet, it only appends to a pending batch capped at 10 changes. That cap and the staged-write behavior are facts annotations cannot convey, and they matter for planning.

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 side-effect scope, then the required follow-up. No filler.

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?

Covers trigger, side effect (proposal only, no account change), batch limit, and the confirmation step. With no output schema, the description still tells the agent what comes back ('returned summaries') and what to do with them. Complete for a 5-param staged-write tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents route, days, from/to, and organization (including the overnight wrap on `to`). The description adds no per-parameter detail, but the mandatory flow of echoing returned summaries to the user gives context beyond the schema. Baseline 3–4; slightly above baseline for the workflow framing.

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+resource: adding a schedule (time window) to a route. The 'propose' semantics distinguish it from patroltech_routes_get_schedules (read) and patroltech_routes_propose_create (new route, not schedule).

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?

Explicit trigger ('when you want to add a schedule to a route'), explicit workflow: show summaries to the user, then call patroltech_proposals_confirm only after agreement. Names the follow-up sibling and the confirmation gate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PatrolTech tools Inspect

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.