Skip to main content
Glama

set_defaults

Saves render defaults so later renders can omit common settings; use clear=true to forget all saved values.

Instructions

Saves render defaults so later renders can leave them out. clear=true forgets all of them.

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

Input Schema

NameRequiredDescriptionDefault
avoidNo
clearNo
modelNo
styleNo
cameraNo
qualityNo
secondsNo

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?

The annotations already declare this is a non-read-only, non-destructive, closed-world write. The description adds genuinely useful behavior the annotations miss: that clear=true erases all stored defaults at once. It does not say whether the other fields merge into existing defaults or replace them wholesale, which matters for a persistence tool.

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?

Two short sentences, zero filler: the primary behavior comes first and the clear=true exception second.

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 7-parameter, no-output-schema write tool, the description covers the most consequential behavior (clear) but leaves merge-vs-replace semantics and per-field meaning implicit. That is adequate but not thorough for a tool whose whole purpose is persistent state.

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?

Schema description coverage is 0%, so the description must explain what the parameters actually mean. It does this for clear only, but the remaining fields (avoid, model, style, camera, quality, seconds) all correspond to knobs defined by the render tool and are connotatively clear. The only real gap is whether each is optional and how merging works.

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?

"Saves render defaults so later renders can leave them out" states a specific verb (saves) and resource (render defaults) plus the effect on downstream renders. It implicitly contrasts with get_defaults, though it never names that sibling.

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?

The phrase "so later renders can leave them out" implies the when-to-use context (pre-configuring a render job), and "clear=true forgets all of them" covers the reset case. There is no explicit guidance on when not to use it, or a pointer to get_defaults for inspection.

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