Skip to main content
Glama
Sign In
ritn3d-mcp

ritn3d-mcp

by printplan3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_floor_plan_image

Checks a floor plan image for format, dimensions, size, and color issues, providing warnings to catch problems before uploading to Ritn3D.

Instructions

Pre-flight check on a floor plan image before sending it to Ritn3D. Reports format, dimensions, file size, color mode, and heuristic warnings (too small, wrong aspect, low contrast). Use this before uploading via the Ritn3D web app or mobile app to catch obvious problems early.

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": {
      "path": "<path>"
    },
    "name": "validate_floor_plan_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFilesystem path to the floor plan image (JPG, PNG, BMP, TIFF, WebP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description fully describes the tool's behavior: it reports on various image properties and heuristic warnings. It implies a safe, non-destructive operation ('pre-flight check'), with no contradictions.

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?

The description is two sentences, each earning its place: first sentence defines functionality, second provides usage context. No redundant or extraneous content.

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 tool with one parameter and no output schema, the description adequately covers what the tool does and when to use it. It lacks detail on heuristic warning criteria, but the overall context is sufficient.

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?

The sole parameter 'path' is fully described in the input schema (100% coverage), listing accepted formats. The description adds no additional semantic meaning beyond what the schema already provides.

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 clearly states the tool performs a 'pre-flight check' on floor plan images, listing specific checks (format, dimensions, file size, color mode, heuristic warnings). It differentiates from sibling tools (estimate_complexity, estimate_render_time) which are about estimation, not validation.

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?

Explicitly states 'Use this before uploading via the Ritn3D web app or mobile app to catch obvious problems early,' providing clear usage context. It does not explicitly state when not to use, but the guidance is sufficient for an agent to decide.

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

Deploy Server

Other Tools