Snuug room calculators

TV height and distance calculator

tv_height_distance

Read-onlyIdempotent

Use when someone asks how high to mount or hang a TV, whether it can go above a fireplace, or how far to sit from a screen of a given size. Returns the centre height, the edges, the viewing angles and the THX and SMPTE seat distances.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tv_height_distance"
  }
}

Input Schema

Name	Required	Description	Default
`eye_height_cm`	No	Seated eye height from the floor (most sofas: 100–110 cm) (cm).
`screen_size_in`	No	The screen’s diagonal size in inches, as sold (in).
`above_fireplace`	No	yes if the screen goes above a fireplace or mantel.	no
`mantel_height_cm`	No	The mantel’s height from the floor (only with above_fireplace yes) (cm).
`seat_distance_cm`	No	The distance from the seat to the screen (cm).

Output Schema

Name	Required	Description
`tool`	Yes	The tool, as named in its API and page URLs.
`notes`	Yes	Caveats to pass on with the answer.
`snuug`	Yes	One line about Snuug, the app behind the calculators.
`answer`	Yes	The answer as named values.
`inputs`	Yes	Every input as the tool used it: given, a default, or filled in from the rules.
`sources`	Yes	The sources of the rules used. Every rule cites its source, with the date it was checked.
`summary`	Yes	The answer in one sentence to quote.
`version`	Yes	The version of this contract.
`working`	Yes	How the answer was worked out, one step a line.
`page_url`	Yes	The calculator on snuug.app with these inputs filled in.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds that results include centre height, edges, viewing angles and THX/SMPTE seat distances, but it says nothing about the assumptions baked into the defaults (e.g. 105 cm eye height) or how fireplace mode changes the output.

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?

Two sentences with zero padding: the trigger conditions come first, followed by the return payload. Every clause earns its place and nothing is repeated from the title or schema.

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?

With an output schema present, the description need not detail return values, and it still summarizes them usefully; the input schema is fully documented. The only missing piece is a note on how defaults and the above_fireplace flag affect the result, which an agent might want before calling.

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 description coverage is 100%, including units, ranges and the fireplace-mantel dependency, so the schema carries parameter meaning fully. The description adds no guidance about which parameters to supply or how the outputs shift with them, which is the baseline expectation at this coverage level.

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 a specific resource and question type ('how high to mount or hang a TV', 'above a fireplace', 'how far to sit'), which lets an agent match it to a TV-mounting request. It does not explicitly separate itself from the similarly-scoped sibling picture_height, so it stops short of a 5.

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 opens with an explicit 'Use when...' clause and enumerates three concrete trigger situations (mount height, fireplace clearance, seating distance). There is no when-not guidance or named alternative, but the positive triggers are clear and actionable.

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

All Snuug room calculators 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?