Skip to main content
Glama

Check the setup

check_setup
Read-onlyIdempotent

Diagnose missing tools or kit startup failures by listing available kits, versions, detected Chrome/ffmpeg/ffprobe paths, invalid settings, and output locations.

Instructions

Shows which kits makersmcp has and their versions, the Chrome and the ffmpeg found for them (and ffprobe while launch-film is on), any setting that leads to no program, and where files are saved. Use it when a tool is missing or a kit fails to start. Settings like CHROME_PATH, FFMPEG_PATH and MAKERSMCP_OUT go in this server's entry in the MCP client's settings, and take effect when the client starts it again.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds non-obvious behavior beyond that: ffprobe only appears while launch-film is on, misconfigured paths surface as 'no program,' and CHROME_PATH/FFMPEG_PATH/MAKERSMCP_OUT live in the MCP client settings and only take effect after a restart. It just doesn't sketch the shape of the report.

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?

Three sentences, front-loaded with what gets reported, then the activation condition, then the remediation detail. The first sentence is long and comma-chained but every clause names a distinct thing that is checked, so nothing is wasted.

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-param, read-only diagnostic with annotations covering the safety profile, the description covers what to expect from the run, when to call it, and how to fix a failure. The only soft spot is that it never confirms the report format (structured vs. text), which matters slightly for a tool whose whole output is a report.

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?

The tool takes no parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The env-var note (CHROME_PATH, FFMPEG_PATH, MAKERSMCP_OUT) is a config input rather than a tool parameter, and it is explained usefully in prose.

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 uses a specific verb (Shows) and enumerates the exact resources inspected: installed kits and their versions, the Chrome and ffmpeg binaries found, ffprobe while launch-film is running, settings that resolve to no program, and the output location. That enumeration distinguishes it from the sibling check_video, check_place_limits, and check_pwa_screenshots tools without needing to name them.

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 an explicit trigger: 'Use it when a tool is missing or a kit fails to start.' That is a concrete failure-mode condition an agent can match. It stops short of stating when not to use it or naming a diagnostic alternative, so it lands below a 5.

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