Skip to main content
Glama
Sign In
vmware-aria-logs

vmware-aria-logs

by apollion69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_dashboards

List saved dashboards for log monitoring and analysis. Compatible with legacy API; returns empty results on Aria Operations for Logs 8.18+.

Instructions

List saved dashboards from Aria Operations for Logs.

Uses the legacy vRLIC API (/vrlic/api/v1/content/dashboards). This endpoint was deprecated in Aria Operations for Logs 8.18+ and will return an empty result on newer appliances.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool uses a deprecated legacy API and will return empty results on newer systems, which is important behavioral context for the agent.

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 concise sentences with no fluff. The first sentence states the purpose, and the subsequent sentences provide critical caveats. Every sentence earns its place.

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?

Given zero parameters and an output schema, the description is fairly complete. It identifies the tool's purpose and its limitation (empty on new appliances). Could mention the return type, but output schema covers that.

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

Parameters4/5

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

There are no parameters, and schema coverage is 100%. The description adds no parameter information, which is acceptable because none exist.

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 clearly states 'List saved dashboards from Aria Operations for Logs', specifying the verb and resource. It does not explicitly differentiate from sibling tools, but the action is distinct from detect_incidents, query_events, etc.

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 the legacy API and deprecation, warning that it returns empty on newer appliances. This provides some usage context but lacks explicit alternatives or when-not-to-use guidance compared to siblings.

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