Skip to main content
Glama

BRAINIAC Identity & Access Security

Analyze authentication patterns

identity-security_authentication-pattern-analyze

Identify abnormal authentication patterns from caller-supplied logs using local time-window correlation. VPN/proxy/shared-network labels reduce confidence. Never proof of compromise from a single login. Price $0.04 USDC. POST /api/v1/identity-security/authentication-pattern-analyze. 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_authentication-pattern-analyze"
  }
}

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

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it discloses that analysis is local (no external enrichment implied), that VPN/proxy/shared-network labels lower confidence, that single-login signals are not proof of compromise, the $0.04 USDC cost, the POST endpoint, and that unpaid calls return 402 without running. What is missing is anything about the shape or granularity of returned findings and whether the call has side effects.

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?

Five short sentences, front-loaded with what the tool does and the confidence caveat before the operational details (price, endpoint, 402). The telegraphic style suits an agent-facing definition, and no sentence is filler.

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

Completeness3/5

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

For a complex 16-parameter tool with no output schema and no annotations, the description covers purpose, interpretation caveats, billing, and the failure mode, but leaves parameter meaning and result shape entirely undocumented. An agent knows what the tool is for but not how to configure it correctly.

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, including nested event/account/policy objects and numerous tuning thresholds (authWindowMinutes, maxTravelKmh, mfaPushThreshold, dormantDays, sharingWindowHours). The description says nothing about these; only 'caller-supplied logs' and 'time-window correlation' loosely hint at the event and window inputs, leaving the agent to read the raw schema.

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 (identify abnormal authentication patterns) plus the input source (caller-supplied logs) and method (local time-window correlation). It does not name or distinguish itself from the specific sibling detectors like impossible-travel or mfa-fatigue, so the agent must infer that this is the general-purpose analyzer.

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 implied rather than stated: 'local time-window correlation' over caller logs, plus an interpretive caveat that a single login is never proof of compromise. There is no explicit when-to-use versus the sibling detectors (e.g., use this for broad sweeps vs. the targeted travel/MFA tools), and no 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