Skip to main content
Glama

refresh_luts

Rescan LUT folders to detect and make newly added LUT files available for use.

Instructions

Rescan the LUT folders so newly added LUT files can be used.

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

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this mutates local state without being destructive. The description adds that the rescan is what makes newly added files usable, which is useful context, but it does not say whether existing LUT references are preserved, whether the scan is expensive, or whether it must be followed by another action.

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 action first and the benefit second, and no redundant or filler wording. Every clause earns its place.

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 zero-parameter, non-destructive maintenance tool with no output schema, the definition covers what it does and why an agent would call it. Minor gaps remain around whether a project must be open and whether the rescan affects currently referenced LUTs.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies no arguments are needed. However, it says nothing about scope (all LUT folders vs. a specific one), which is the only semantic question a zero-param tool could raise.

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?

States a specific verb and resource ('Rescan the LUT folders') plus the outcome ('newly added LUT files can be used'), so the agent knows exactly what operation occurs. It does not distinguish itself from the sibling refresh_bins, which handles a different asset type, leaving that differentiation to inference.

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 clause 'so newly added LUT files can be used' implies the trigger condition (new LUTs were added outside the app), but this is embedded in the purpose rather than framed as when-to-use guidance. There is no statement about when not to call it, whether it is safe to call repeatedly, or how it relates to refresh_bins.

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