Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_get_account_activity_logs

Retrieve account activity logs to monitor user actions and system events for auditing and troubleshooting purposes.

Instructions

Retrieve activity logs for the account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo

Implementation Reference

  • tools/account.js:22-24 (handler)
    The handler function for 'pressable_get_account_activity_logs' which calls the API to retrieve account activity logs.
    handler: async (args) => {
    return await api.get('/account/activity_logs', args);
}
  • tools/account.js:12-25 (registration)
    The tool definition and registration for 'pressable_get_account_activity_logs'.
    {
    name: 'pressable_get_account_activity_logs',
    description: 'Retrieve activity logs for the account.',
    inputSchema: {
        type: 'object',
        properties: {
            page: { type: 'integer' },
            per_page: { type: 'integer' }
        }
    },
    handler: async (args) => {
        return await api.get('/account/activity_logs', args);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely says 'Retrieve activity logs for the account' without mentioning read-only nature, pagination behavior, data volume, or any other behavioral nuance. This adds no value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it is under-specified. It is not verbose, but it does not provide enough information to be considered appropriately sized for a tool with pagination parameters. The sentence is front-loaded but lacks substance.

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

Completeness1/5

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

For a tool with two optional parameters and no output schema, the description is severely incomplete. It does not explain what the parameters do, how to use them, or what the response contains. The agent cannot infer key usage details from this description.

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

Parameters1/5

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

The input schema has two parameters (page, per_page) with no descriptions, and schema description coverage is 0%. The description does not mention these parameters at all, failing to compensate for the lack of schema-level detail.

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 states a clear verb (Retrieve) and resource (activity logs for the account), making the primary purpose understandable. However, it does not explicitly differentiate from the sibling tool pressable_get_account_activity_log_actions, relying on the noun 'logs' vs 'actions' to distinguish. Thus it is clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The description simply states the action with no context about pagination or typical use cases.

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

Deploy Server

Other Tools