Rendreal

Set display units

session_set_units

DestructiveIdempotent

Record the measurement units to show this customer their artwork sizes in.

Sizes default to IMPERIAL (inches) — the US market. Call this ONLY when the customer explicitly asks to see METRIC (mm/cm), or asks to switch back. The choice sticks for the rest of the session and applies to every prepress and artwork-spec surface, including the upload page.

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": {
      "session_id": "<session_id>",
      "unit": "<unit>"
    },
    "name": "session_set_units"
  }
}

Input Schema

Name	Required	Description	Default
`unit`	Yes	The measurement system a customer's geometry is rendered in. A session preference, default imperial; distinct from `artifex.product.UnitFormat`, the upstream wire tag that is normalised to mm at ingest and discarded.
`session_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The description adds useful behavior beyond the annotations: the choice persists for the rest of the session and applies to every prepress and artwork-spec surface, including the upload page. However, annotations declare destructiveHint=true, and the description never explains what is overwritten or whether an existing preference is replaced. That leaves a meaningful gap for a session-mutating tool.

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?

The description is front-loaded with the core purpose, then gives the default, the only-call condition, and the persistence scope. It is efficient overall, with mild redundancy around the customer explicitly asking.

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 two-parameter session preference tool with annotations and an output schema, the description covers purpose, default, trigger condition, and persistence scope well. The main omission is the destructive/overwrite behavior flagged by annotations and the undocumented session_id.

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 50%: the unit enum is documented in the schema, while session_id is not. The description reinforces unit meaning (IMPERIAL default, METRIC as mm/cm, US market) but adds nothing about session_id or its required role.

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 states a specific verb and resource: record the measurement units used to display artwork sizes to a customer. That is distinct from the session, prepress, and artwork-spec siblings, so an agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

Usage is explicit and conditional: call this ONLY when the customer explicitly asks for METRIC (mm/cm) or asks to switch back. The default (IMPERIAL) is stated, so the agent knows when not to call the tool.

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

All Rendreal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?