Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect account sharing

identity-security_account-sharing-detect

Identify suspicious account-sharing patterns from multi-device, multi-location, and near-simultaneous authentications. Shared-network context is treated as a mitigating factor. Price $0.04 USDC. POST /api/v1/identity-security/account-sharing-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_account-sharing-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 carries the whole burden, and it does contribute real behavior: a $0.04 USDC price, POST to a named endpoint, a 402 on unpaid calls that 'do not run', and a false-positive suppression rule for shared networks. What it omits is substantial — nothing about whether the operation mutates state (it appears to be a read-only analysis but this is never stated), no rate limits, no mention of the accepted input modalities (csv/json/text/file/files/events/accounts/policies), and no indication of what a verdict looks like.

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?

Four compact sentences, front-loaded with what is detected before commercial and protocol details. The endpoint path largely restates the tool name, but the price and 402 rule earn their space as operationally relevant facts; nothing is padded or redundant.

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 top-level parameters, deep nested schemas, no annotations, and no output schema, this description is far too thin — an agent still cannot tell which of the many optional input channels to populate, what shape the evidence must take, or what the response contains. The payment and endpoint facts are covered, but the input contract and return semantics are not.

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 and policy objects plus eight numeric tuning thresholds (sharingWindowHours, maxTravelKmh, mfaPushThreshold, etc.), so the description needed to compensate and does not. The phrase 'multi-device, multi-location, and near-simultaneous authentications' faintly gestures at events[].deviceId, latitude/longitude and timestamp fields, and 'shared-network' at isSharedNetwork, but no parameter is named or explained.

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 gives a specific verb and resource — 'Identify suspicious account-sharing patterns' — and names the concrete signals it keys on (multi-device, multi-location, near-simultaneous authentications), which separates it from siblings like impossible-travel-detect or mfa-fatigue-detect even without naming them. It is clear at a glance, though it never explicitly contrasts itself with the closest sibling.

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?

There is no statement of when to choose this tool over the other identity-security detectors, no prerequisites, and no note on what inputs are mandatory (the schema says everything is optional). The only usage-adjacent content is a mitigation rule ('shared-network context is treated as a mitigating factor'), which tells the agent how results are interpreted rather than when to invoke it.

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