Renderior

Rug size calculator

rug_size

Read-only

Which standard rug size fits a living room (from the room's size, leaving bare floor at the walls) or goes under a dining table (from the table's size, so chairs stay on the rug when pulled out). kind "living" takes the room in feet; kind "dining" takes the table in inches. 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>"
    },
    "name": "rug_size"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	living: room size in feet. dining: table size in inches.	living
`width`	Yes	Room width in feet (living) or table width in inches (dining).
`length`	Yes	Room length in feet (living) or table length in inches (dining).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare this is a read-only, closed-world calculation, and the description adds genuinely useful context about the rule being applied and that the answer references a source page. However, that source-page mention sits somewhat uneasily with openWorldHint=false without being a true contradiction, and the description never says what the returned recommendation looks like when no standard size fits, which matters given there is no output schema.

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?

Two sentences, both earning their place, with the two modes and their units front-loaded before the provenance note. The parenthetical clauses are dense but readable, and nothing is padded.

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 three-parameter, side-effect-free calculator with full schema coverage and annotations, the definition covers the mode choice, the units, and the nature of the answer. The only real gap is edge-case behavior when no standard size fits, which an agent could not predict from this text.

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% and every property already documents its unit convention and the living/dining meaning, so the description is largely restating what the schema provides. The one thing it adds is the purpose-level framing of why length and width are interpreted differently per kind. Baseline 3 is appropriate.

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 states precisely what the tool computes (a standard rug size) and enumerates its two distinct input modes: fitting a living room from the room's dimensions, or sizing a rug to go under a dining table. The verb is implicit ("which size fits") rather than an explicit action, and no sibling tool is named, but the residential-scale calculational scope is unmistakable against a sibling list of other furniture-size calculators.

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 clearly tells the agent which mode to choose and what each mode expects: kind "living" takes the room in feet, kind "dining" takes the table in inches. It also states the design intent behind each mode (leaving bare floor at the walls vs. chairs staying on the rug when pulled out). No exclusions or failure conditions are mentioned, such as what happens for an unusually small room.

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

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