Skip to main content
Glama
Sign In

Renderior

by com.renderior
OverviewDiscussionsAdmin

Curtain length calculator

curtain_length
Read-only

Curtain panel length, the stock length to buy, rod width and total fabric width for a window. Style is how the curtain meets the floor: float, kiss, break or puddle. 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": {
      "width": "<width>",
      "floor": "<floor>"
    },
    "name": "curtain_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboveNoHow far above the frame the rod goes, in inches. Default 6.
floorYesDistance from the top of the window frame to the floor, in inches.
styleNofloat (half an inch off the floor), kiss, break (1 to 2 inches extra) or puddle (3 to 6 inches extra). Default kiss.kiss
widthYesWindow width across the outside of the frame, in inches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a non-destructive, closed-world read operation. The description adds useful context beyond them: results are a "designer rule of thumb" rather than exact engineering, and the answer contains a link to a source page, which tells the agent the response includes explanatory provenance. It does not describe the shape of the returned numbers or units, leaving that gap.

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?

Three short sentences with no filler, and the outputs are front-loaded so an agent scanning the first clause already knows what it gets back. The opening noun phrase is slightly clipped but not confusing.

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?

There is no output schema, so the description properly enumerates the four returned values, and it clarifies the misleadingly named style parameter. Combined with a fully described input schema and readOnly annotations, an agent has enough to invoke it correctly; only units for the outputs are unstated.

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 all four parameters are already documented with units and defaults. The prose restates the style enum values (float, kiss, break, puddle) that the schema already explains, and mentions rod width, which is an output rather than an input, so it adds little meaning beyond the schema.

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 names the exact outputs of the calculator (panel length, stock length to buy, rod width, total fabric width) for a window, which is a concrete and specific statement of purpose. It lacks an explicit verb like "calculates" and never names a sibling, but the subject matter alone separates it cleanly from the other sizing calculators such as rug_size or chandelier_size.

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?

Usage is only implied: the agent can infer this is the tool for curtain projects on a window with a known frame-to-floor distance. There is no explicit statement of when to use it versus the sibling sizing tools, and no mention of prerequisites such as needing inches or having the rod position decided.

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