Skip to main content
Glama
PatrolTech MCP server

PatrolTech MCP server

Official

Account context

patroltech_account_get_context
Read-onlyIdempotent

Lists the organizations and locations an account can access, with names, IDs, and roles, so you can identify the right organization before using operational tools.

Instructions

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.example.com): 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 observedv0.2.9

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description is free to add what they cannot: that an unlisted organization is not accessible, that results carry names, ids, roles and locations, and that no tool returns tokens or credentials. The dashboard disconnect note adds a trust/compliance dimension that is not derivable from any structured field.

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?

Front-loaded with purpose, then the when-to-use and when-not rules, then the access caveat. The dashboard disconnect sentence is tangential to tool selection but short and serves a real security purpose, so it does not seriously dilute the definition.

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?

For a zero-parameter read with no output schema, the description supplies the return shape (org names/ids, role, location names/ids), the access boundary, and the ordering rule relative to the operational tools. An agent has everything needed to call it at the right moment and interpret the result.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends its words on scope and return shape instead of inventing parameter guidance.

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 and resource: lists the organizations the account can access, with role in each, plus their locations with names and ids. It also implicitly separates itself from the operational siblings by noting that the other tools take the organization name, so an agent can place it in the workflow without opening another 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?

Gives an explicit positive trigger ('Call it first when unsure which organization or location a question is about') and an explicit negative one ('Do not use when you already know the organization and need operational data'). It also names the handoff convention (other tools take the organization name), leaving nothing to inference.

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