Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect dormant-account risk

identity-security_dormant-account-risk-detect

Identify risks from inactive but enabled accounts using caller-supplied account inventory and optional recent auth events. Hygiene signal only—not confirmed compromise. Price $0.03 USDC. POST /api/v1/identity-security/dormant-account-risk-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_dormant-account-risk-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

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose pricing ($0.03 USDC), the endpoint, and that unpaid calls return 402 without running, which is genuinely useful. It also adds the important caveat that results are a hygiene signal rather than confirmed compromise. It omits what the response contains and whether detection thresholds are configurable from output.

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 and the key caveat before operational details. Every sentence carries information, though the raw endpoint path adds little for an agent that already knows the tool name.

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 objects and no output schema, the description leaves most of the input contract unaddressed and says nothing about return values. It covers the commercial and safety framing well but is thin relative to the tool's complexity.

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 deeply nested accounts and events objects. The description only gestures at 'account inventory' and 'recent auth events', leaving asOf and the eight tuning parameters (dormantDays, maxTravelKmh, mfaPushThreshold, windows) entirely unexplained.

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 risks from inactive-but-enabled accounts using caller-supplied inventory plus optional auth events. The 'inactive but enabled' scoping meaningfully separates it from the sibling detector family. It stops short of naming an alternative 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?

Implies context by saying the caller supplies the account inventory and that events are optional, which tells the agent what input is required. It never states when to reach for this tool versus 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