Skip to main content
Glama
Sign In

PatrolTech

by online.patroltech
OverviewDiscussionsAdmin

Account context

patroltech_account_get_context
Read-onlyIdempotent

Lists the organizations this PatrolTech account can access (names and ids), with the role in each, and their locations (names and ids). An organization not listed here is not accessible with this account. Call it first when unsure which organization or location a question is about; the other tools take the organization name. Do not use when you already know the organization and need operational data. The user can review or disconnect this connection in the PatrolTech dashboard (https://dashboard.patroltech.online): user menu, Connected apps ("Aplicaciones conectadas" in Spanish). No tool returns tokens or credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful access-context details: unlisted organizations are inaccessible, other tools take the organization name, and no tool returns credentials. The dashboard/disconnect note is extra but relevant to account trust.

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?

The purpose is front-loaded in the first sentence, and the usage guidance follows directly. The dashboard and credential notes are slightly tangential but still useful and not excessive.

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 compensates by explaining the returned content: organization names and ids, the account's role in each, and location names and ids. It also explains the access boundary and when the tool should be used, which is sufficient for this zero-parameter read-only 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?

The tool has zero parameters, so there is no parameter semantics burden; the baseline for zero-parameter tools is 4. The description does not need to explain inputs beyond indicating that it takes none.

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?

The description states a specific verb and resource: it lists accessible organizations and locations with names, ids, and roles. It clearly distinguishes this account-context tool from operational sibling tools such as incidents, rounds, and patrolers.

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?

It gives explicit guidance to call it first when unsure which organization or location a question is about, and says not to use it when the organization is already known and operational data is needed. It does not name a specific alternative sibling, but the boundaries are clear.

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