Skip to main content
Glama

eschaton_preflight_check

Analyze source code before sandbox dispatch to detect infinite loops, fork bombs, and banned syscalls, blocking hazardous snippets from reaching the microVM.

Instructions

In-memory AST syntax and hazard detection (<50µs): Detects infinite loops, fork bombs, and banned syscalls before microVM dispatch.

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": {
      "code": "<code>",
      "language": "<language>"
    },
    "name": "eschaton_preflight_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code to analyze
languageYesProgramming language (python, javascript, c, cpp, bash, go)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that analysis is in-memory, sub-50µs, and non-executing ('detection ... before dispatch'), which tells the agent the code is not run. However it never states what happens on a hit — whether the tool raises an error, returns a findings list, or merely flags — which is the critical behavior for a safety gate with no output schema.

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?

A single front-loaded sentence-fragment: operation, latency, detection targets, and placement in the pipeline, with no filler. Slightly dense with the parenthetical timing, but every clause conveys actionable information.

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?

The input side is fully covered by a 100%-documented two-parameter schema, so the tool is callable as written. With no output schema, the description should explain the shape of a result (pass/fail vs. structured findings, and whether a detected hazard aborts the call) — that gap is the main incompleteness for a validation gate.

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%: both 'code' and 'language' are documented in the schema, including the supported language list. The description adds no syntax, size, or format constraints beyond that (e.g., whether code is a string, file path, or snippet), so baseline 3 applies.

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 a concrete operation and resource — 'in-memory AST syntax and hazard detection' over source code — and enumerates the specific hazards found (infinite loops, fork bombs, banned syscalls). It is clearly a static-analysis gate rather than execution. It stops short of distinguishing itself from close siblings such as eschaton_sanitize_check or eschaton_complexity_profile, leaving the agent to infer the boundary.

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?

'before microVM dispatch' implies the usage context: this is a pre-execution gate to run on code prior to submitting it. That is useful implied guidance, but there is no explicit when-to-use versus when-to-skip statement and no named alternative among the sibling analysis tools.

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