Skip to main content
Glama

logs

Read-only

Read recent app logs—JS console output, native errors, and crash messages—to diagnose crashes, frozen screens, or blank UI trees and confirm expected log lines fired.

Instructions

Read recent app logs from the device — JS console output, native errors, and crash messages from the app under test (not full system logs). Check after a crash, a frozen screen, or an unexpected blank tree, and to confirm an expected log line fired. Pass the previous response's cursor as since to get only lines that arrived after it.

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

Input Schema

NameRequiredDescriptionDefault
tailNoMaximum lines to return, newest kept (default 100, max 500).
sinceNoOnly lines newer than this cursor (use the previous response's `cursor` value).
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered; the description adds real behavioral context on top: the log scope, the diagnostic situations it serves, and the incremental-fetch pattern using the prior response's cursor. It does not describe truncation behavior or the response shape (no output schema exists), which keeps it off a 5.

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?

Three tight sentences, front-loaded with the resource and its scope, then diagnostic triggers, then the incremental-fetch instruction. No filler or repetition of the tool name.

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?

For a three-optional-parameter read tool with a fully documented schema and readOnly annotation, the description covers what is read, when to read it, and how to page forward incrementally. Only the return/truncation behavior is unstated, a minor gap given no output schema is defined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the round-trip contract: pass the previous response's cursor as `since` to get only newly arrived lines. That is meaningful usage semantics the property description alone does not spell out as a workflow.

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?

"Read recent app logs from the device" gives a specific verb plus resource, and the parenthetical enumerates exactly what is captured (JS console output, native errors, crash messages) while excluding full system logs. An agent knows precisely what this returns and how it differs from a system-log or run-report tool.

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 names concrete triggers — after a crash, a frozen screen, an unexpected blank tree, or to confirm an expected log line fired — which is strong when-to-use guidance. It stops short of naming an alternative tool or a when-not condition, so it falls just short of the top band.

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