Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_logs

Retrieve recent macOS system logs filtered by process, subsystem, or time range to debug applications.

Instructions

Get recent logs from macOS system. Use for debugging macOS apps.

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_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
processNoFilter by process name (e.g., 'WorxVPNExtension', 'Safari')
maxLinesNoMaximum number of log lines to return (default: 200)
subsystemNoFilter by subsystem (e.g., 'com.worxvpn.ios')
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?

No annotations provided, so the description bears full burden. It states 'get recent logs' implying read-only but does not disclose any side effects, authentication requirements, or rate limits. Does not explain what 'recent' means or the format of the logs, lacking essential behavioral details.

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?

Two short, direct sentences with no filler. The main action is front-loaded ('Get recent logs'). Every word earns its place.

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, no output schema, and four parameters, the description is too minimal. It does not explain the return format, how to interpret logs, or how this tool relates to other log tools. For a debugging tool, more context is necessary.

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%, meaning all four parameters are documented in the input schema. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as no extra value is provided.

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?

Clearly states 'Get recent logs from macOS system' specifying the resource (logs) and action (get). Differentiates from device/simulator log tools by mentioning 'macOS system', but does not explicitly distinguish from siblings like search_logs or stream_logs.

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?

Says 'Use for debugging macOS apps', providing a usage context. However, it does not specify when not to use this tool or suggest alternatives like search_logs or stream_logs, which is needed given the number of sibling log tools.

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