Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect service-account anomalies

identity-security_service-account-anomaly-detect

Analyze unusual service-account activity such as interactive logins, off-hours use, and high application/IP diversity from caller-supplied events. Price $0.04 USDC. POST /api/v1/identity-security/service-account-anomaly-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_service-account-anomaly-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
Behavior3/5

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

With no annotations supplied, the description does carry real behavioral weight: it discloses the $0.04 USDC price, the POST endpoint, and the important fact that unpaid calls return 402 and do not execute. It still says nothing about side effects, determinism, runtime, 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?

Three short sentences, front-loaded with the analytical purpose, followed by commercial and failure-mode facts. No filler, though the raw endpoint path is arguably low-value for an agent compared to threshold guidance.

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 tool with 16 parameters, deep nested schemas, no annotations, and no output schema, the description is far too thin. An agent would know what it computes and what it costs, but not how to shape the payload or what the result looks like.

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 events, accounts, and policies arrays and eight tuning thresholds (dormantDays, maxTravelKmh, mfaPushThreshold, etc.). The description only hints that events are supplied by the caller and explains none of the input alternatives (csv/json/text/file/files) or threshold semantics.

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 description names a specific verb ('Analyze') and resource ('service-account activity') and enumerates the exact signals detected: interactive logins, off-hours use, and application/IP diversity. That is enough to tell it apart from siblings like impossible-travel or mfa-fatigue, though it never explicitly names those alternatives.

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

Usage Guidelines2/5

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

The phrase 'from caller-supplied events' implies the caller must provide the telemetry, which is a useful precondition. But there is no statement of when to choose this tool over the closely related authentication-pattern-analyze or impossible-travel tools, and no when-not-to-use guidance.

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