Analyze User Activity
analyze_user_activityRent Manager user login activity and concurrent-user counts (UserLog, 3).
Use for questions like:
"How many users were logged in at one time yesterday?"
"What's our peak concurrent user count this week / last week?"
"How many people logged into Rent Manager on Monday?"
"Show me failed login attempts"
Returns total sessions, distinct users, failed login attempts, the PEAK number of users logged in simultaneously (with timestamp), and either a per-day peak table (multi-day range) or an hourly concurrency profile (single-day range). Org-wide by nature — there is no property scope.
Caveat for ranges that include today: RM records a session only at LOGOUT, so users currently logged in are not in the log yet — today's recent hours UNDERSTATE true concurrency. Completed (past) days are accurate.
Args: start_date: MM/DD/YYYY. Defaults to 6 days ago (a 7-day window). end_date: MM/DD/YYYY. Defaults to today.
``location`` (optional): a Rent Manager Location ID, a comma-separated
list, or ``"all"`` to run across every Location on this connection (see
``list_locations``). Blank = all Locations if the connection has several,
else its only Location. Output is labelled per Location; a Location that
can't be reached is listed as skipped. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.
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": "analyze_user_activity"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | No | ||
| location | No | ||
| start_date | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |