Skip to main content
Glama
Sign In

Renderior

by com.renderior
OverviewDiscussionsAdmin

Chandelier size calculator

chandelier_size
Read-only

What diameter and height of chandelier suits a room, and how far it should hang. Over a dining table, the diameter follows the table's width instead of the room. Gives the designer rule of thumb; the page linked in the answer shows the sources.

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": {
      "length": "<length>",
      "width": "<width>",
      "ceiling": "<ceiling>"
    },
    "name": "chandelier_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNoDining table width in inches when the light hangs over a table; leave out or 0 otherwise.
widthYesRoom width, in feet.
lengthYesRoom length, in feet.
ceilingYesCeiling height, in feet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish read-only and closed-world behavior. The description adds that results follow a designer rule of thumb and that the answer links to sources, which is useful provenance, but it does not specify output units, limits, or calculation assumptions beyond the rule-of-thumb caveat.

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?

Three short sentences, front-loaded with the core output and then the important dining-table exception. No wasted wording; provenance is compactly included.

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 simple read-only calculator with four fully described inputs and no output schema, the description supplies the core outputs and the key special case. It could be slightly more complete about output units, but nothing critical for correct invocation is missing.

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 coverage is 100%, so all parameters are already documented. The description adds a conceptual relation not fully in the schema: over a dining table, the diameter is based on table width instead of room width. That meaning goes beyond the individual field descriptions.

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 clearly states that it computes chandelier diameter and hanging height for a room, with a special dining-table case. It is specific enough to separate it from sibling calculators by object, though it does not explicitly name an alternative or exclusion.

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?

It implies the tool is used when sizing a chandelier and explains the dining-table condition that selects the table path. It gives no explicit when-not-to-use guidance or comparison to related siblings such as pendant_spacing, so selection rests on implied context.

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

All Renderior toolsInspect
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