Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_capabilities

Check which photoreal renderers are usable now and whether the FreeCAD Render addon imports, so you can pick a working renderer for render_photoreal without trial and error.

Instructions

Report which photoreal renderers are usable right now, and whether the FreeCAD Render addon imports — so you can pick a working renderer for render_photoreal instead of discovering availability by trial and error.

Takes no arguments. Resolves each renderer's binary exactly as render_photoreal would (ANKUSDRIVE__PATH env override -> FreeCAD prefs -> PATH -> per-OS install dirs), but renders nothing and changes no settings.

Returns {addon_importable (bool), default_renderer ('Povray'), platform, available (sorted list of ready renderer names for the renderer= argument), renderers: {name: {available, param_key, batch, binaries, and either path (the resolved binary) or install_hint}}, materials (library card names usable as render_photoreal's material= argument, present only when the addon imports), and addon_error (present only when the addon does not import)}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it states that it renders nothing, changes no settings, resolves binaries exactly like render_photoreal (including the fallback chain), and returns a detailed capability report. Side-effect and resolution semantics are fully disclosed.

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 front-loaded with purpose and usage, then covers resolution behavior and return shape. Every sentence is informative, and no sentence is wasted despite the length, which is justified by the lack of an output schema.

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 zero-argument, no-annotation tool with no output schema, the description supplies an unusually complete return contract: the fields, their meanings, and conditional presence. An agent has everything needed to call it and interpret the result correctly.

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?

The tool takes zero parameters and the input schema is empty, so the baseline is 4. The description confirms 'Takes no arguments,' which is sufficient but adds no parameter detail beyond what the schema already conveys.

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 states a specific verb and resource: reporting which photoreal renderers are usable and whether the FreeCAD Render addon imports. It explicitly connects the purpose to render_photoreal, so an agent can distinguish it from generic capability/status tools like solve_capabilities or setup_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains exactly when to use it: before render_photoreal, to pick a working renderer instead of discovering availability by trial and error. The alternative behavior is named, and the no-argument constraint is stated up front.

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