Skip to main content
Glama

suggest_settings

Read-only

Provides starting settings for a video goal and surfaces high-scoring local renders, so you can launch ComfyUI projects from proven configurations.

Instructions

Settings to start with for a goal ("calm portrait", "lively dance", "quick test"), plus the best-scored videos made on this PC so far (scores come from review_video(judge=true) and auto_fix).

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

Input Schema

NameRequiredDescriptionDefault
goalNo
modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful provenance (scores originate from review_video(judge=true) and auto_fix) and scope ('on this PC so far'), though the local scope is partly redundant with openWorldHint=false. It does not disclose how many videos/settings are returned or whether results are cached or recomputed.

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?

A single front-loaded sentence with zero filler; the primary output (settings for a goal) comes first and the secondary output follows. The nested parentheticals make it slightly dense but every clause carries information.

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 read-only, two-optional-parameter tool with no output schema, the description conveys what comes back (settings plus ranked local videos) and where the ranking comes from, which is the main thing an agent needs. The uncovered 'model' parameter and the absence of any indication of result volume keep it from being fully complete.

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 0% for the two optional parameters, so the description must compensate. It does partially by giving concrete goal values in quotes ('calm portrait', 'lively dance', 'quick test'), which conveys the expected free-text style. However, the 'model' parameter is never mentioned, leaving half the input surface undocumented anywhere.

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 the concrete deliverable: starting settings tailored to a goal (with quoted example goals) plus top-scored local videos. That is a specific verb-less but unambiguous resource description, distinguishable from get_defaults or review_video. It stops short of an explicit action verb like 'recommends' or 'returns', but the intent is clear.

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 can infer this is a pre-flight step before choosing settings for a build. There is no explicit when-to-use framing, no exclusion of alternatives such as get_defaults, and no statement about when this is unnecessary. The mention of review_video(judge=true) and auto_fix explains where scores come from, not when to call this tool.

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