Skip to main content
Glama

Change the time of day

relight_room

Paid (like one colour in the quality it was painted in: 1 credit standard, 2 hd, 3 ultra). Relight a finished interior visualization as day, evening or night, with lamps on or off, keeping the wall colour. Needs project_id and the color_key returned by visualize_room.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "color_key": "<color_key>",
      "time": "<time>"
    },
    "name": "relight_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesTime of day
lampsNoLamps on
color_keyYescolor_key of the painted result, e.g. "c1"
project_idYesproject_id from visualize_room

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already identify a non-read-only, non-idempotent, open-world operation, and the description adds a credit-cost model (1/2/3 depending on quality) plus the guarantee that wall colour is preserved. It does not detail output construction or whether the original image is retained, but the cost and preservation behavior are useful beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and contains the key purpose, inputs, and cost, but the opening parenthetical about "one colour in the quality it was painted in" is awkwardly worded and places cost before the central relighting action. The second sentence is much clearer and front-loads the prerequisite, so the overall structure is serviceable but not clean.

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 paid, non-idempotent generation tool with no output schema, the description covers the required inputs, credit cost, target time, lamps, and preserved wall colour. It does not explain what is returned or how the relit result is retrieved, leaving a notable gap for an open-world mutation.

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 100%, so the input schema already documents project_id, color_key, time, and lamps. The description adds the provenance of project_id/color_key from visualize_room, but the cost-quality parenthetical is ambiguous and does not clearly map to any of the four parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Relight," and a specific resource, "a finished interior visualization," and enumerates the supported target times (day, evening, night) and lamp state. It also ties the tool to the output of visualize_room via color_key, which helps distinguish it from a first-pass visualization tool.

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

Usage Guidelines4/5

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

It establishes the prerequisite sequence: use it on a finished visualization and supply project_id plus the color_key returned by visualize_room. It does not explicitly say when not to use it or name alternatives, but the post-visualize context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources