Skip to main content
Glama
Sign In
Seq MCP Server

Seq MCP Server

by itachiuchihadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

seq_tail_events

Wait for and capture recent or live Seq log events within a timeout window to monitor streams and troubleshoot issues.

Instructions

Wait for and capture recent or live stream events from Seq within a specified timeout window.

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

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of events to capture (1-100, default: 10).
filterNoOptional Seq filter expression to apply to the stream.
workspaceNoOptional workspace identifier.
timeoutSecondsNoTime window in seconds to wait for events (1-30, default: 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at blocking behavior ('Wait for') and a timeout window, but the timeout is already covered by the schema; it omits permission requirements, side effects, idempotency, and whether it blocks until the timeout or returns as soon as count is reached.

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?

A single, front-loaded sentence that states the core action and scope without any filler. Every word earns its place.

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 full schema coverage and no output schema, the description is adequate for basic invocation but lacks usage alternatives and behavioral context (e.g., blocking nature, return completeness). It leaves the agent with gaps when choosing between this and sibling search/query tools.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds no parameter-level meaning beyond what the schema provides, making 3 the appropriate baseline.

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?

States a specific verb phrase ('Wait for and capture'), resource ('recent or live stream events from Seq'), and scope ('within a specified timeout window'). However, it does not explicitly differentiate itself from siblings such as seq_search or seq_query beyond the implied contrast of live/recent versus historical.

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?

The phrase 'Wait for and capture recent or live stream events' implies the tool is used when live or recent event monitoring is needed, but no explicit when-to-use, when-not-to-use, or named alternatives are provided.

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