Skip to main content
Glama
Sign In
Scout MCP Server

Scout MCP Server

Official
by scoutos-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

logs

Retrieve recent application events for any app using its slug, with an optional line count to limit the number of entries returned.

Instructions

Get recent logs for an app

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": {
      "slug": "<slug>"
    },
    "name": "logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesApp slug
linesNoNumber of lines (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get,' implying a read-only operation, but does not disclose output format, ordering, pagination, or any potential side effects. This is minimal disclosure for a tool that interacts with app infrastructure.

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 a single, efficient sentence with no redundant words. It is appropriately sized for a simple tool, though it could incorporate a bit more behavioral context without becoming verbose.

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?

Given the simplicity (2 params, no output schema, no annotations), the description provides the core purpose but leaves out behavioral details such as what the logs look like or any limitations. It is adequate for an agent to understand the tool's basic function, but it does not fully cover all context an agent might need (e.g., ordering, format).

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 description coverage is 100%, with both parameters (slug and lines) described in the schema. The description adds no extra meaning beyond 'recent logs,' but the schema already documents the parameters adequately, so the baseline of 3 is appropriate.

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 action ('Get') and the resource ('recent logs for an app'). Among sibling tools like app_list, deploy, and port_get, logs is uniquely identified as the log retrieval tool, so it distinguishes itself from all siblings.

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

Usage Guidelines3/5

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

The description implies usage: call this tool when you need an app's recent logs. It provides no explicit alternatives or exclusions, but no sibling tool offers log retrieval, so the intended use is clear. No prerequisites or when-not-to-use guidance is given.

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

Deploy Server

Other Tools