Skip to main content
Glama

My recent security activity

security_activity_list
Read-onlyIdempotent

Recent security events on your own account, newest first: sign-ins (browser, system, device, country), session sign-outs, and verified contact changes. IP addresses are not shown. Sign-in history covers the last 30 days. Page with next_cursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoValue of next_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe read, but the description adds real operational context: results are newest-first, IP addresses are deliberately omitted, coverage is capped at the last 30 days, and pagination runs through next_cursor. These are non-obvious constraints an agent could not derive from the annotations alone. Return shape detail is partial but adequate for a list endpoint.

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?

Dense and front-loaded: scope and contents first, then the two important constraints (no IPs, 30-day window), then pagination. No filler sentences and nothing repeated from the title or annotations.

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?

For a read-only paginated list with no output schema, the description carries its weight by describing what each record contains, ordering, and the coverage window. The only real gap is the limit parameter's default and maximum, which the schema does supply, so nothing critical is missing for correct invocation.

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?

With 50% schema coverage, the cursor parameter is documented in the schema and the description reinforces it by tying it to the response's next_cursor field, which is genuinely useful. The limit parameter is never mentioned in the description, so half the parameter surface relies solely on the schema. Baseline 3 is appropriate.

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?

Names a specific verb+resource (list recent security events) and enumerates the exact event types returned: sign-ins with browser/system/device/country detail, session sign-outs, and verified contact changes. Scope is pinned to 'your own account.' It does not explicitly say how it differs from siblings such as security_sessions_list or profile_activity_list, so it falls short of a 5.

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?

Usage is implied by the scope ('your own account') and the event-type enumeration, which tells an agent what it will get. However, there is no explicit when-to-use guidance, no 'use X instead for Y' routing, and the near-neighbor security_sessions_list is never named or contrasted.

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