Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get User Sign Ins

get_user_sign_ins
Read-only

Get sign-in logs for a specific user within the last N days.

Instructions

Get sign-in logs for a specific user within the last N days.

Requires AuditLog.Read.All permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "get_user_sign_ins"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoThe number of past days to retrieve logs for (default: 7).
user_idYesThe unique identifier (ID) of the user.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, so the safety profile is known. The description adds a genuinely useful behavioral fact not in structured data: it requires the AuditLog.Read.All permission, telling the agent an auth precondition exists. It stops short of mentioning result caps, pagination, or throttling for large day ranges.

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?

Two sentences, zero waste, with the core operation front-loaded and the permission prerequisite as a separate, clearly scannable statement.

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

Completeness4/5

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

An output schema exists so return values need no explanation, parameters are fully documented, and the auth requirement is disclosed. The only meaningful gap is lack of sibling disambiguation against get_user_audit_logs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented. The description's 'last N days' phrasing corroborates the days parameter but adds no format or constraint details (e.g., maximum allowed days) beyond the 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 ('Get sign-in logs') with a clear scope of 'for a specific user within the last N days.' It is distinguishable from most siblings, though it does not explicitly contrast with the closely related get_user_audit_logs.

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?

The description implies usage (fetching one user's sign-in history over a time window) but gives no explicit when-to-use or when-not-to-use guidance. It never names or excludes alternatives such as get_user_audit_logs, which an agent must disambiguate on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.