Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Dashboard users and roles

patroltech_users_list_roles
Read-onlyIdempotent

Use when you want to know who has access to the dashboard and with which role. Returns the dashboard users with their role (Admin, Editor or Viewer) and scope (whole organization or one location), and what each role can change. Only an organization Admin can read it. Do not use when you need the guards.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the exact return payload (user, role, scope, plus what each role can change) and an authorization prerequisite ('Only an organization Admin can read it'), which is exactly the kind of constraint 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with the use case, then the return shape, then the permission constraint. The trailing 'Do not use when you need the guards' is the weakest sentence — it adds a term not used elsewhere and does not name a real alternative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return shape, and it does: users, roles, scope, and role capabilities. Combined with the stated Admin-only access requirement and the well-documented single parameter, an agent has enough to decide and call correctly; only the vague 'guards' pointer leaves a gap.

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?

There is a single optional parameter and schema description coverage is 100%, including a cross-reference to patroltech_account_get_context and the multi-organization condition. The description adds no additional meaning about the organization parameter, so 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 and resource — lists dashboard users with their role (Admin/Editor/Viewer) and scope (organization vs. location) — which is concrete and distinguishable from the patrol/incident/round siblings. It never names an actual sibling tool, and the exclusion refers to 'guards', a term that does not appear in any sibling name (the catalog uses 'patrollers'), so the differentiation is only partial.

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?

'Use when you want to know who has access to the dashboard' gives a clear trigger, and 'Do not use when you need the guards' provides an explicit exclusion. The exclusion is weakened because it does not point to a concrete alternative tool in the sibling list, leaving the agent to guess which tool covers guard/patroller data.

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