Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stream_logs

Stream live system logs for a set duration to capture real-time output during specific actions. Filter by process name for targeted monitoring.

Instructions

Stream live logs for a specified duration. Useful for capturing logs during an action.

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

Input Schema

NameRequiredDescriptionDefault
processNoFilter by process name
durationSecondsNoHow long to stream logs (default: 10 seconds, max: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only states duration and filtering, but omits whether the call is blocking, how logs are returned (stream vs batch), or any side effects. Inadequate for a streaming operation.

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 concise sentences: first states core function, second adds a usage example. No wasted words.

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 and two optional parameters, the description is adequate but incomplete. It does not explain return format, whether the stream ends automatically, or behavior when filters match nothing.

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% with parameter descriptions. The description adds only the phrase 'for a specified duration', which mildly reinforces durationSeconds but adds no substantial meaning beyond the schema.

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?

Clearly states verb 'stream', resource 'live logs', and adds contextual use case 'capturing logs during an action'. Distinguishes from siblings like get_logs and search_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?

Provides a vague usage hint ('useful for capturing logs during an action') but no explicit when-to-use or when-not-to-use, nor comparisons to alternatives like stream_simulator_logs.

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