Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_vpn_logs

Retrieve VPN process logs from Console.app by filtering for WorxVPN extension. Customize output with line count or timeframe.

Instructions

Get logs specifically for WorxVPN extension - filters for VPN-related processes

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

Input Schema

NameRequiredDescriptionDefault
maxLinesNoMaximum number of log lines (default: 300)
lastMinutesNoHow many minutes of logs to fetch (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It mentions filtering for VPN processes but omits details like read-only nature, default parameter values, or that it returns system logs. The parameters are not mentioned in the description.

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 a single, clear sentence with no wasted words. It is front-loaded with the main purpose. However, it could include a brief note on parameters or usage without becoming verbose.

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?

For a simple tool with two optional parameters and no output schema, the description is adequate. It provides the essential purpose and distinguishes from siblings, but lacks details on return format or parameter behavior, which are covered by the 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?

Schema coverage is 100%, so parameters are well-documented in the schema. The description adds no extra meaning beyond what is already in the input schema, meeting the baseline.

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 gets logs for WorxVPN and filters for VPN-related processes, distinguishing it from generic log tools like get_logs or get_device_logs.

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 on when to use this tool versus alternatives like get_logs or search_logs. The description does not indicate prerequisites or contexts where this tool is preferred.

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