Skip to main content
Glama

Environment preflight

doctor
Read-only

Checks prerequisites for generating a narrated product-demo MP4—Node, ffmpeg, browser/Chrome, TTS/STT endpoint, API key, Playwright, and installed skill—to flag missing dependencies before rendering.

Instructions

Check prereqs: node, ffmpeg, Chrome (or the AIDEMO_CHROME_CHANNEL / AIDEMO_CHROME_EXECUTABLE browser in use), TTS/STT endpoint (flags LLM-only servers like Ollama), API key, playwright + its ffmpeg helper (records the take; installed on the first take unless AIDEMO_NO_AUTO_INSTALL=1), installed skill.

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

Input Schema

NameRequiredDescriptionDefault
dirNorepo to check for an installed skill

Output Schema

NameRequiredDescriptionDefault
ghYes
okYes
ttsYes
nodeYes
skillYes
apiKeyYes
chromeYes
ffmpegYes
browserYes
endpointYes
playwrightYes
engineVersionYes
recorderFfmpegYesPlaywright's ffmpeg helper the built-in capture records with

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / recorderFfmpeg
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "autoInstall": {
      +          "description": "the first take installs it (off with AIDEMO_NO_AUTO_INSTALL=1)",
      +          "type": "boolean"
      +        },
      +        "found": {
      +          "type": "boolean"
      +        },
      +        "install": {
      +          "description": "exact command to install it",
      +          "type": "string"
      +        },
      +        "path": {
      +          "type": "string"
      +        },
      +        "revision": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "found",
      +        "path",
      +        "revision",
      +        "install",
      +        "autoInstall"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Playwright's ffmpeg helper the built-in capture records with"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "engineVersion",
      -  "node",
      -  "ffmpeg",
      -  "chrome",
      -  "browser",
      -  "gh",
      -  "endpoint",
      -  "apiKey",
      -  "tts",
      -  "playwright",
      -  "skill",
      -  "ok"
      -]New value: +[
      +  "engineVersion",
      +  "node",
      +  "ffmpeg",
      +  "chrome",
      +  "browser",
      +  "gh",
      +  "endpoint",
      +  "apiKey",
      +  "tts",
      +  "playwright",
      +  "recorderFfmpeg",
      +  "skill",
      +  "ok"
      +]
  2. Changed2 schema fields changedv0.16.1
    • addedOutput schema / properties / browser
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "channel": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "executablePath": {
      +      "type": "string"
      +    },
      +    "found": {
      +      "type": "boolean"
      +    },
      +    "source": {
      +      "enum": [
      +        "default",
      +        "channel",
      +        "executable"
      +      ],
      +      "type": "string"
      +    },
      +    "version": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "description",
      +    "found"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "engineVersion",
      -  "node",
      -  "ffmpeg",
      -  "chrome",
      -  "gh",
      -  "endpoint",
      -  "apiKey",
      -  "tts",
      -  "playwright",
      -  "skill",
      -  "ok"
      -]New value: +[
      +  "engineVersion",
      +  "node",
      +  "ffmpeg",
      +  "chrome",
      +  "browser",
      +  "gh",
      +  "endpoint",
      +  "apiKey",
      +  "tts",
      +  "playwright",
      +  "skill",
      +  "ok"
      +]
  3. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only give readOnlyHint=true, so the description carries real weight here and delivers: it names the relevant env vars (AIDEMO_CHROME_CHANNEL, AIDEMO_CHROME_EXECUTABLE, AIDEMO_NO_AUTO_INSTALL), discloses that playwright's ffmpeg helper gets auto-installed on the first take, and warns that LLM-only servers like Ollama get flagged. It does not say whether the tool itself reports remediation steps, but the side-effect context is substantially beyond the annotation.

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?

One front-loaded sentence that opens with the operative verb and list of checks; parentheticals are dense but each qualifies a specific check rather than padding. Slightly hard to scan due to stacked parentheticals, but nothing is redundant.

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

Completeness4/5

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

For a zero-required-param read-only diagnostic with an output schema (so return values need no explanation), the description covers what is checked and the notable environment variables. Only the expected outcome on failure and the relationship to 'probe' are left unstated.

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 100% and the single 'dir' parameter is documented as 'repo to check for an installed skill'. The description's mention of the 'installed skill' check corroborates that, but adds no syntax, default, or omission behavior beyond the schema. Baseline 3 is 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?

States a specific verb ('Check') and enumerates the concrete prereqs inspected: node, ffmpeg, Chrome channel/executable, TTS/STT endpoint, API key, playwright + ffmpeg helper, installed skill. The scope is unmistakable, but it never distinguishes itself from the sibling 'probe', which an agent could plausibly reach for instead.

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?

Usage is only implied by the title 'Environment preflight' and the nature of the checks; there is no explicit 'run this before record/render' instruction, no statement of when not to run it, and no mention of the 'probe' alternative. An agent can infer the preflight role but must guess the sequencing.

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