Skip to main content
Glama

app_logs

Retrieve console logs and JavaScript errors from a live Expo app to diagnose runtime issues, filter by level or search, and optionally clear captured entries.

Instructions

Console logs and JS errors captured in the app.

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

Input Schema

NameRequiredDescriptionDefault
clearNo
levelNo"error" = errors only, "warn" = warnings and errors
limitNodefault 50
sinceNoonly entries after this cursor (returned as "cursor")
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and fails to mention that the `clear` flag destroys the captured log buffer, that `limit` defaults to 50 so results are truncated by default, or that `since` implies cursor-based incremental reads. A destructive, spelled 'clear' parameter is hidden entirely behind the schema.

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

Conciseness3/5

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

It is a single sentence with zero waste and front-loads the resource, but it is under-specified rather than concise – one more sentence on truncation defaults and the destructive clear flag would earn its place.

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

Completeness2/5

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

Five optional parameters, a destructive clear flag, default result limiting, no output schema and no annotations – the description addresses none of these. An agent could reasonably call it and silently wipe or truncate the very logs it wanted.

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 60%: level (with enum semantics explained), limit (default 50) and since (cursor) are documented in the schema, while clear and search have no description anywhere. The description adds no parameter meaning beyond the schema, so it neither compensates for the gap nor is it the sole source.

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?

The description names the resource precisely – console logs and JS errors captured in the app – which is enough to tell it apart from a device-level or network tool at a glance. It stops short of explicitly contrasting with siblings like app_network, and it omits the verb (retrieve/list), so the agent must infer that this is a read.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to reach for this when debugging JS exceptions versus inspecting network traffic with app_network or checking app_status. No prerequisites, no exclusions, no mention of when a cleared buffer means the call is pointless.

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