Skip to main content
Glama

vme_get_activity

Retrieve recent HPE VME activity and audit logs—including provisioning, changes, and logins—to review infrastructure events and investigate changes.

Instructions

Get recent activity/audit log from HPE VME — provisioning, changes, logins.

Args: max: Max results (default: 50). gateway_id: Target gateway (optional).

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

Input Schema

NameRequiredDescriptionDefault
maxNo
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never states that this is a read-only operation, does not define the recency window, does not mention whether results are paginated or truncated at `max`, and gives no indication of the response shape.

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?

The purpose sentence is front-loaded and free of filler, and the Args block is short. The Args block largely duplicates what the JSON schema already exposes, which is mild waste but not harmful.

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?

This is a simple two-parameter read tool, so a short description is defensible, but with zero annotations and no output schema the definition leaves the safety profile, the meaning of "recent," and the result shape entirely unspecified.

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 0%, so the description is the only prose about the parameters, and it does at least name both of them. However, it only restates the defaults already in the schema (max=50) and adds no real meaning — no units for `max`, no statement of what filtering by `gateway_id` actually scopes.

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 gives a specific verb+resource ("Get recent activity/audit log from HPE VME") and enumerates the event classes covered (provisioning, changes, logins), so an agent knows exactly what the tool returns. It does not explicitly differentiate itself from any sibling, which keeps it just 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The closest thing to guidance is the word "recent," which is never defined, so an agent cannot tell what conditions make this the right call versus another inspection tool.

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