Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_logs

Retrieve recent system logs from VergeOS virtualization platforms to monitor operations, troubleshoot issues, and track cluster activities.

Instructions

Get recent system logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of log entries to retrieve (default 50)

Implementation Reference

  • Core handler function in VergeOSAPI class that fetches the most recent system logs from the /api/v4/logs endpoint, applying the specified limit and sorting by newest first.
    async getLogs(limit = 50) {
      return this.request(`/api/v4/logs?limit=${limit}&sort=-created`);
    }
  • src/index.js:502-513 (registration)
    Tool registration definition in the TOOLS array, including name, description, and input schema. Used by listTools handler.
    {
      name: "get_logs",
      description: "Get recent system logs",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of log entries to retrieve (default 50)",
          },
        },
      },
  • Dispatch handler in the CallToolRequestSchema handler that invokes the get_logs tool logic via api.getLogs.
    case "get_logs":
      result = await api.getLogs(args?.limit || 50);
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'recent' but doesn't clarify time ranges, ordering, or format of logs. For a read operation with no annotation coverage, this leaves critical gaps in understanding how the tool behaves.

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 description is very concise with a single phrase, 'Get recent system logs', which is front-loaded and wastes no words. However, it might be overly terse given the lack of context, slightly reducing effectiveness.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'recent' means, the log format, or return values, leaving the agent with insufficient context for a tool that retrieves system data.

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?

The input schema has 100% coverage with a clear description for the 'limit' parameter, so the baseline is 3. The tool description adds no additional parameter information beyond what the schema provides, such as default behavior or constraints, so it doesn't enhance semantics.

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

Purpose3/5

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

The description 'Get recent system logs' clearly states the verb ('Get') and resource ('system logs'), making the purpose understandable. However, it lacks specificity about what 'recent' means and doesn't differentiate from sibling tools like 'get_alarms' or 'get_cluster_status', leaving ambiguity about scope.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_alarms' and 'get_cluster_status' that might overlap in monitoring contexts, there's no indication of when this tool is appropriate or what distinguishes it, leaving the agent to guess.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dvvincent/vergeos-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server