Skip to main content
Glama

check_setup

Verifies API key, ffmpeg, saved voices, and output folder, then fixes each detected issue so speech and caption generation run correctly.

Instructions

Check the API key, ffmpeg, saved voices and output folder, with a fix for every problem found.

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

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses a non-obvious trait — that it can apply a fix for every problem found, implying state mutation to config or filesystem — but does not say whether fixes are automatic, confirmed, or reversible, nor what side effects occur on the host machine.

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?

A single front-loaded sentence with the verb first and the four checked items enumerated; there is no filler and the surprising capability (auto-fix) is included rather than buried.

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?

For a zero-argument diagnostic tool with no output schema and no annotations, the description should say what a check returns (a pass/fail report?) and what the fix step actually touches. It covers the inputs to the check well but leaves the outcome and side effects underspecified.

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 zero parameters, so the schema baseline of 4 applies; there is nothing for the description to disambiguate. The enumerated check targets do hint at what the tool acts on, which is a small bonus.

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 action (check) and enumerates the exact resources examined: API key, ffmpeg, saved voices, output folder. An agent can immediately tell this is a diagnostics tool and distinguish it from the sibling narration/transcription tools, though it never explicitly contrasts itself with them.

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: an agent infers it should call this before narrating or transcribing to verify prerequisites. There is no explicit 'call this when X is failing' or 'call before first use' instruction, and no statement about what to do if the fix step is declined.

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