Skip to main content
Glama

get_logs

Read-only

Retrieve recent Kit app log entries filtered by severity, channel, or text to debug issues and monitor application behavior.

Instructions

Get the latest entries of the Kit app's log, read from its log file since the bridge extension started, by level, channel or text.

Each entry shows its channel and the first 200 characters of its message, saying how many more it has. search matches the whole message: an entry whose match lies past the 200 gets a matched: line with the match in its line. Kit's file holds Info and above by default; verbose lines need Kit started with both --/log/level=verbose and --/log/fileLogLevel=verbose. A script's own exception, print and stderr come back in execute_script's answer and never reach Kit's log; carb.log_error and the other carb.log_* calls in a script do.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many of the latest entries; the buffer keeps 2000
searchNoOnly messages containing this anywhere, in any case
channelNoOnly channels containing this, e.g. "omni.physx"
min_levelNoThe lowest severity to return; every level when empty

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / search / description
      Previous value: -"Only messages containing this, in any case"New value: +"Only messages containing this anywhere, in any case"
  2. First observedv0.2.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and closed-world, so safety is covered. The description adds real behavior beyond that: entries are truncated to 200 characters with a remainder count, matches past the truncation surface as a matched: line, and verbose lines require startup flags. It does not discuss the 2000-entry buffer limit or ordering, which the schema partially covers.

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?

Front-loaded with purpose and filter axes, then behavior, then the script-log caveat. Dense but every sentence carries information; the long compound sentences around truncation and verbosity take a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only, four-parameter tool with an output schema and full schema coverage needs modest description, and this supplies truncation format, match behavior, and level gating. The only notable omission is ordering/pagination beyond the schema's buffer note, which is minor.

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%, including enum values for min_level and per-parameter descriptions, so baseline applies. The description does add value on `search` semantics (matches the whole message, not just the visible excerpt) and on the level gate, pushing it just past a pure baseline read.

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?

States a specific verb and resource (get the latest log entries), names the source (Kit app's log file since the bridge extension started), and enumerates the filter axes (level, channel, text). No sibling tool reads logs, so an agent can identify it immediately.

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?

Explains the practical condition for verbose output (Kit must be started with --/log/level=verbose and --/log/fileLogLevel=verbose) and explicitly routes script output away to execute_script, telling the agent when this tool will not have the data it wants. It stops short of naming a full alternative for log browsing, but the exclusions are concrete.

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