Skip to main content
Glama
JOCOIN94

silotek-serial-mcp

by JOCOIN94

query_serial_logs

Search serial logs for keywords or errors using regex. Returns matching lines (newest first) to identify boot sequences, errors, or state changes.

Instructions

[언제 호출] 특정 키워드/에러/마커를 버퍼에서 찾을 때. 예: 부팅 완료 문구, 'ERROR', 특정 상태 출력의 등장 여부.

[port 규약] get_recent_logs 와 동일 — 복수 포트면 지정, 미지정 에러 시 ports 목록에서 골라 재호출.

[무엇을 반환] 정규식 pattern 매칭 라인들(최신 우선 max_results개, 반환은 시간 오름차순, 접힌 묶음 표기 포함). 매칭 0이면 그 문구가 아직 안 나온 것 — 사람에게 해당 동작을 요청하거나 더 기다린 뒤 재조회하라.

[루프 단계] 결과 확인(표적 검색).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYes
max_resultsNo
portNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses return format (matching lines, newest first, time ascending, collapsed grouping) and behavior when no match is found. This is adequate for a query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with clear sections (언제 호출, port 규약, etc.), making it easy to parse. It is moderately concise with no extraneous content.

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?

For a tool with 3 params, no output schema, and no annotations, the description covers usage context, return format, and error handling. However, it omits details like whether pattern is regex or literal, and the exact effect of max_results.

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 0%, so description must compensate. It explains pattern (keyword/error/marker) and port (protocol), but max_results is only mentioned by name without full meaning. Some semantic value is added, but not comprehensive.

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's purpose: to find specific keywords/errors/markers in a buffer. It distinguishes itself from siblings like get_recent_logs by focusing on pattern matching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-call (searching for specific strings) and port protocol (similar to get_recent_logs). It also advises on no-match scenarios. However, it lacks explicit when-not-to-use conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JOCOIN94/silotek-serial-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server