Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_logs

Search recent console and iOS device logs by text or regex to quickly find matching entries, with options to limit results and search duration.

Instructions

Search through recent logs for a specific string or regex pattern

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": {
      "query": "<query>"
    },
    "name": "search_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText or regex pattern to search for in logs
maxLinesNoMaximum matching lines to return (default: 100)
useRegexNoTreat query as a regex pattern (default: false)
lastMinutesNoHow many minutes of logs to search (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

Without annotations, the description only mentions 'recent logs' but does not explain the default time range, rate limits, or that it is a read-only operation. It also does not describe any side effects or authentication requirements.

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, concise sentence that conveys the core functionality without unnecessary words. It is front-loaded with the key verb and resource.

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?

Given no output schema, the description does not explain the return format or structure. It also does not specify whether results are full log lines or truncated. However, the tool is simple enough that this gap is moderate.

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?

All parameters have descriptions in the schema, so the description adds no extra meaning beyond what is already provided. Baseline score of 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 tool searches through logs for a string or regex pattern. It uses a specific verb ('search') and resource ('logs'), and distinguishes from siblings like 'get_logs' (fetching without search) and '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 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 alternatives such as 'get_logs' or 'get_logs_by_level'. The description lacks context about prerequisites or exclusions.

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