Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_logs_by_level

Retrieve macOS and iOS logs filtered by severity level (fault, error, warning, info, debug), with optional process and time range constraints for targeted debugging.

Instructions

Get logs filtered by severity level (fault, error, warning, info, debug)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "level": "<level>"
    },
    "name": "get_logs_by_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesLog level to filter by
processNoFilter by process name
maxLinesNoMaximum log lines (default: 200)
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 are provided, so the description should disclose behavioral traits. It only mentions severity level filtering but omits details about other parameters (process, maxLines, lastMinutes), output format, pagination, or side effects. The tool name suggests it only filters by level, but the schema includes additional filters not described.

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?

The description is a single, efficient sentence with no extraneous words. It is front-loaded with the core action and filter criteria.

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 the absence of annotations and output schema, the description is too minimal. It does not explain the return format, how logs are ordered, or defaults for optional parameters. For a tool with four parameters and a potentially large dataset, more context is needed.

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% description coverage, providing clear descriptions for all four parameters. The description adds a list of allowed levels, which is already in the enum. It does not add new semantics beyond what the schema provides, so baseline 3 is appropriate.

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 verb 'Get', the resource 'logs', and the specific filter 'by severity level' with the allowed levels enumerated. It distinguishes from siblings like 'get_logs' which are likely unfiltered, and 'get_device_logs' or 'get_simulator_logs' which filter by device/simulator.

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 is provided on when to use this tool versus the many sibling tools such as 'get_logs' (generic), 'search_logs', 'get_crash_logs', or 'get_vpn_logs'. The description does not mention any prerequisites or when to avoid using it.

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