Skip to main content
Glama
Sign In
Edgegap MCP Server

Edgegap MCP Server

Official
by edgegap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get container logs for a deployment

edgegap_get_deployment_logs
Read-only

Retrieve stdout, stderr, and crash output for a deployment to diagnose errors or unexpected server exits using the crash exit code before redeploying.

Instructions

Retrieve stdout/stderr and crash output for a deployment. Call this whenever a deployment errors or a server exits unexpectedly — the crash exit code usually identifies the problem faster than redeploying does. Logs for stopped deployments are only retained if Endpoint Storage was configured on the version beforehand.

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": {
      "request_id": "<request_id>"
    },
    "name": "edgegap_get_deployment_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id of the deployment.
max_charactersNoTruncate logs to this length (500-50000), keeping the tail. Default 8000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • changedInput schema / properties / max_characters / description
      Previous value: -"Truncate logs to this length, keeping the tail. Default 8000."New value: +"Truncate logs to this length (500-50000), keeping the tail. Default 8000."
    • changedInput schema / properties / max_characters / maximum
      Previous value: -50000New value: +9007199254740991
    • changedInput schema / properties / max_characters / minimum
      Previous value: -500New value: +-9007199254740991
  2. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already cover the safety profile, and the description adds valuable context about crash output and retention for stopped deployments. It does not contradict the annotations and adds operational insight beyond them.

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 sentences, front-loaded with the core action, followed by usage guidance and a retention caveat. Every sentence adds useful information without repetition.

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

Completeness5/5

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

For a two-parameter read-only log retrieval tool with full schema coverage and annotation safety hints, the description is complete enough. It covers purpose, when to call it, output content, and the stopped-deployment retention caveat.

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%, so request_id and max_characters are already documented. The description adds little parameter-specific meaning beyond saying it retrieves deployment logs, which makes the baseline 3 appropriate.

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 states a specific verb and resource: retrieving stdout/stderr and crash output for a deployment. It clearly distinguishes the tool's content from generic deployment lookup siblings, though it does not explicitly name when to use it instead of edgegap_get_deployment or edgegap_get_deployment_metrics.

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?

It gives a clear trigger: call this whenever a deployment errors or a server exits unexpectedly. The rationale about crash exit codes is useful, but it does not mention explicit alternatives or when not to use it.

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