Bot-Hosting.net

Read console logs

deployments_logs

Read-onlyIdempotent

Read the last N lines of the console log, cleaned of colour codes and progress spam. A build or install takes MINUTES: pass waitSeconds (e.g. 25) to wait server-side before reading, instead of calling this again and again - polling in a loop is how a whole conversation gets eaten by npm output. Returns the live state alongside.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "deployments_logs"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`size`	No	Default 100.
`waitSeconds`	No	Wait up to this long BEFORE reading, returning early once the process has died or gone idle (no new output, CPU quiet). The wait is server-side and costs nothing. settled:false at the end means it is still working (installing): wait again.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real behavior: output is stripped of colour codes and progress spam, the wait is server-side and "costs nothing", and settled:false means still working. The one gap is the return shape beyond "live state alongside".

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 the action and its output guarantee, then the key usage advice. The npm-output aside is colorful but slightly padded; the core content still earns its space.

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 3-param read tool with no output schema, it covers the wait/settled loop well, but leaves the `id` format unstated (deployment id vs slug?) and the return payload only loosely described as "live state alongside". An agent can call it, but may need a trial to know exactly what comes back.

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 67% and the description adds meaning on top: it motivates waitSeconds with a suggested value and the polling-avoidance rationale, and implicitly defines size as "last N lines". The required `id` parameter is never characterized in either the schema or the description, which is the remaining hole.

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?

"Read the last N lines of the console log, cleaned of colour codes and progress spam" gives a specific verb, resource, and even a data-shaping guarantee, which an agent can act on directly. It never names or contrasts with the sibling deployments_searchLogs, so an agent must still infer which log reader to pick.

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 gives concrete when-to-use guidance: pass waitSeconds (e.g. 25) rather than re-invoking repeatedly, and it explains the rationale (builds take minutes). It stops short of naming an alternative tool for searching/filtering logs, so the sibling boundary remains implicit.

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

All Bot-Hosting.net tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?