Skip to main content
Glama

auth_events

Read-onlyIdempotent

Retrieve newest-first login, probe, and lease audit events with attached source and account identity details, optionally filtered by source and limited by row count.

Instructions

Identity event stream (crawl_identity_events), newest first: the login/probe/lease audit trail with the identity (source + account alias) attached. Same projection the Console auth panel renders.

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": "auth_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax rows (default 20, hard cap 200).
sourceNofilter to one source's identities.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuinely useful behavior: results are returned newest-first and each row carries identity attribution (source + account alias). Pagination beyond the limit cap is still unexplained.

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?

Content is front-loaded: the resource and ordering come first, then the content detail. The internal function name '(crawl_identity_events)' and the Console-parity clause add little for an agent, but the text is otherwise tight.

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?

With an output schema present, return values need not be described, and annotations carry the safety profile; the description still covers source of records, ordering, and attribution. The main omission is sibling disambiguation versus auth_status, which is a small but real gap for a zero-required-param read tool in a crowded auth_* family.

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%, and the schema already documents both `limit` (default 20, hard cap 200) and `source` (filter to one source's identities). The description's mention of 'source + account alias' is attached to the record shape rather than the filter, adding little beyond the schema — the baseline 3 applies.

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 the resource precisely as an identity event stream and enumerates its content (login/probe/lease audit trail), plus the attached identity fields and ordering. It does not explicitly contrast with auth_status or the other auth_* siblings, so the differentiation is only implicit.

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?

Calling it an 'audit trail' implies the audit/history use case, and the Console-auth-panel reference hints at parity with the UI view. However, there is no explicit 'use this when you want history, use auth_status when you want current state' routing guidance or any precondition statement.

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