Skip to main content
Glama

Is Clips Kitty running

engine_status

Confirm the Clips Kitty engine is running and retrieve its version before starting or monitoring clip jobs.

Instructions

Whether the engine is up, and which version it is.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden; it does convey that this is a non-mutating probe returning liveness plus a version string, which is meaningful behavioral information for a zero-parameter tool. It omits the important failure semantics — whether a down engine produces an error or a negative status value — and any auth or rate-limit notes.

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 short sentence with the core fact (is it up) front-loaded ahead of the secondary fact (version). No filler and nothing trailing at the end.

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 health-check tool with no parameters and no output schema, the definition is close to sufficient, but since no output schema exists the description is the only source for the return shape, and it never specifies field names or what a 'not up' result looks like. Adding one clause about the response would make it complete.

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, so there is nothing for the description to disambiguate; the schema is trivially complete. The mention of version reporting is extra value, though it concerns the response rather than inputs.

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 specific resource (the engine) and two concrete facts it reports: liveness and version. That is enough to separate it from the surrounding status siblings like job_status or queue_status, which concern jobs and queues rather than the engine itself, though it never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this before other operations, on connection failure, or instead of job_status/queue_status/publish_status. The only cue is the tool name and title, so the agent must infer usage from context alone.

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