Skip to main content
Glama
Sign In
ritn3d-mcp

ritn3d-mcp

by printplan3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

estimate_render_time

Estimate the rendering time for a 3D model from a floor plan, returning a low/expected/high range in seconds to inform users of expected wait time.

Instructions

Rough estimate of how long the Ritn3D pipeline will take to render a 3D model from a given plan. Returns a low/expected/high range in seconds. Useful for telling users 'this will take about a minute' versus 'this may take five minutes.'

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": {
      "complexity": "<complexity>"
    },
    "name": "estimate_render_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
complexityYesComplexity label, e.g. from estimate_complexity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the estimate is rough, returns a low/expected/high range in seconds, and implies no side effects. Could explicitly state it's read-only, but the name and context suggest non-destructive.

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: first defines purpose and output, second provides usage context. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, description adequately covers what the tool does, what it returns, and how to use it with the sibling tool.

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% with enum description. Description adds cross-reference to sibling 'estimate_complexity' as a source for complexity label, adding value beyond schema.

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?

Description clearly states the tool estimates render time for 3D models using the Ritn3D pipeline, with verb 'estimate' and resource 'time'. Distinguishes from siblings by focusing on time rather than complexity or validation.

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?

Implies usage when a render time estimate is needed ('useful for telling users...'), but does not mention when not to use or compare with alternatives like estimate_complexity.

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