Skip to main content
Glama
Sign In
HAOps MCP Server

HAOps MCP Server

by tbranzov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

haops_get_audit_log

Retrieve a system-wide audit log showing all changes across the platform, filtered by action, entity type, and pagination (admin only).

Instructions

Get system-wide audit log (admin only). Shows all changes across the platform with filters.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
limitNoResults per page (default: 50, max: 100)
actionNoFilter by action type (e.g., owner_changed, status_changed, created)
entityTypeNoFilter by entity type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It indicates read-only behavior by 'shows all changes', but does not detail error handling for non-admin users, pagination behavior, or data scope beyond 'all changes across the platform'.

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?

The description is two sentences, front-loaded with the core purpose, and contains no redundant information. Every word serves a purpose.

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

Completeness3/5

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

No output schema is provided, yet the description does not hint at the return format or structure of the audit log entries. Pagination is implied by schema but not mentioned in description. Adequate but not thorough for a tool with no output schema.

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?

Input schema has 100% parameter description coverage (page, limit, action, entityType). The description only says 'with filters' without adding extra meaning or context beyond what the schema already provides. Baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves 'system-wide audit log' with 'filters', specifying it's 'admin only'. It distinguishes from sibling tools like haops_get_activity by indicating system-wide scope.

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 mentions 'admin only' as a prerequisite but does not explicitly contrast with similar tools like haops_get_activity or specify when to use this tool instead of others. Usage context is implied but not fully elaborated.

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