Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Propose editing a location

patroltech_locations_propose_edit

Use when you want to change the name or address of a location. 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

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_locations_propose_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name. Omit it if it does not change.
addressNoNew address. Omit it if it does not change. It cannot be left empty.
locationNoCurrent name of the location. Ask for it only if there are several.
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.7/5.0
Behavior5/5

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

Annotations only mark it as non-read-only and non-destructive, and the description adds the crucial semantics: it stages a proposal in a pending batch rather than applying anything, and is capped at 10 changes. It also discloses the two-step confirm flow, which the annotations cannot express.

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 with zero waste: usage condition first, then the no-side-effect behavior and batch limit, then the required follow-up action. Everything is front-loaded and actionable.

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, but the description signals that the call returns summaries to be surfaced to the user, and it covers the batching constraint and the confirmation dependency. Nothing an agent needs to invoke this safely 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 name, address, location, and organization is already fully documented in the schema. The description restates the field scope but adds no format or syntax 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 action (change the name or address of a location) and scopes it precisely to those two fields. An agent can distinguish it from patroltech_checkpoints_propose_edit and from the confirm/cancel siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it, notes the pending-batch cap of 10 changes, and prescribes the workflow: show the returned summaries to the user and call patroltech_proposals_confirm only after they agree. That names both the alternative and the condition that selects it.

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