Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect impossible travel

identity-security_impossible-travel-detect

Detect geographically inconsistent logins from supplied timestamps and locations. Accounts for VPN/proxy/shared networks and legitimate-travel labels; a single unusual pair is not proof of compromise. Price $0.05 USDC. POST /api/v1/identity-security/impossible-travel-detect. Unpaid calls return 402 and do not run.

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": "identity-security_impossible-travel-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
eventsNo
accountsNo
policiesNo
dormantDaysNo
maxTravelKmhNo
mfaPushThresholdNo
mfaWindowMinutesNo
authWindowMinutesNo
sharingWindowHoursNo
serviceBaselineWindowHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior: VPN/proxy/shared-network and legitimate-travel awareness, a false-positive caution, the $0.05 USDC price, and that unpaid calls return 402 without running. However, it never states that this is a non-mutating analysis, says nothing about how much data must be supplied, processing limits, or what the response contains.

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 every subsequent sentence adds something concrete. The price/endpoint/402 lines are operational boilerplate that could be compressed, but not wasted.

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

Completeness2/5

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

For a 16-parameter tool with nested events/accounts/policies arrays, no annotations, and no output schema, the description is thin. It omits which input channel to use, that some event data is required for any detection, and the meaning of the tunable windows, leaving an agent unable to construct a valid, meaningful call from the prose alone.

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

Parameters2/5

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

Schema description coverage is 0% across 16 parameters, so the description must compensate and largely does not. It hints at event fields via 'timestamps and locations' and the VPN/proxy/shared-network/labels handling, but says nothing about the csv/json/text/file/files input forms, asOf, or the threshold parameters (maxTravelKmh, authWindowMinutes, mfaPushThreshold, sharingWindowHours, etc.), all of which are undocumented anywhere.

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?

The first sentence gives a specific verb and resource ('Detect geographically inconsistent logins') and the second narrows the analysis to VPN/proxy/shared-network and legitimate-travel context. This is enough to separate it from siblings such as mfa-fatigue-detect or account-sharing-detect without opening a schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the tool analyzes supplied login events, and the caution that 'a single unusual pair is not proof of compromise' shapes how a result should be acted on. There is no explicit statement of when to prefer this over the other identity-security detectors, nor any prerequisites beyond payment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources