Skip to main content
Glama

My connection activity log

portal_mcp_activity_list
Read-onlyIdempotent

The tools your own connected AI apps and keys ran on your account, newest first: tool name, success or failure, duration, which app. Arguments and results are not stored, so this log says what ran and when, not what data was read. History is kept 90 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": "portal_mcp_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNoread = only tools that read data, write = only tools that change data. Omit for both.
limitNo
cursorNoValue of next_cursor from the previous page.
only_failedNo

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: newest-first ordering, a 90-day retention window, the fact that arguments and results are not stored, and cursor-based paging.

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?

Three tight sentences, front-loaded with what the log contains, then the key limitation, then retention and paging. No filler; every clause carries information an agent needs.

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 five optional parameters and no output schema, the description does the important work of enumerating returned fields and stating the retention and no-payload limits. The main residual gap is the limit parameter and the exact days values, which the schema covers but the description does not reinforce.

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 coverage is only 40%, so the description must compensate. It explains cursor paging ('Page with next_cursor') and the 90-day window that bounds the days parameter, and the success/failure mention hints at only_failed, but limit and the specific days enum values (1/7/30/90) are left entirely to 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 resource and scope: the tool calls made by the user's own connected AI apps and keys, with the returned fields enumerated (tool name, success/failure, duration, app). This implicitly separates it from account-wide siblings like security_activity_list or profile_activity_list, though it never names an alternative.

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 statement ('your own connected AI apps and keys'), and the 90-day retention plus 'arguments and results are not stored' tells the agent what questions this log can and cannot answer. However, there is no explicit when-to-use/when-not guidance or routing to the other activity-log siblings.

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