CineFlow Studio

cineflow_hardware_profile

Inspect local hardware (OS, CPU, RAM, GPU, VRAM) to recommend a suitable ComfyUI memory profile for your system.

Instructions

Inspect local computer hardware (OS, CPU, RAM, GPU, VRAM) and recommend the optimal ComfyUI memory profile (rtx_24gb, rtx_16gb, rtx_12gb, apple_silicon, or cloud_only).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Inspect' implies a read-only operation, and the enumerated profile values clarify the recommendation domain, but the description does not explicitly confirm that no system changes occur, whether it reads the local machine only, or what the response format will be.

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?

The description is a single front-loaded sentence that states the inspection target first, then the recommendation and its possible values. Every clause earns its place, and the enumerated profile names prevent ambiguity about expected output values.

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 simple, zero-parameter inspection tool, the description covers what is inspected and what recommendation is produced. Because there is no output schema, it should ideally clarify whether the response includes both raw hardware details and the selected profile; it implies both but does not fully specify return shape.

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 has zero parameters, so there is no parameter semantics to add. The baseline for zero parameters is 4, and the schema coverage is already complete at 100%.

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 uses a specific verb, 'Inspect,' and names the exact resource: local computer hardware including OS, CPU, RAM, GPU, and VRAM. It also states the secondary output, a ComfyUI memory profile recommendation from five enumerated values. It is clear, but it does not explicitly differentiate itself from sibling tools such as cineflow_comfy_config_get or cineflow_comfy_config_set.

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 implied: an agent would call this to learn the machine's capabilities and obtain the appropriate ComfyUI memory profile. However, the description does not state when to prefer this over checking config directly, nor does it mention prerequisites or when not to use it.

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

Deploy Server