Skip to main content
Glama
fboldo

openscad-mcp-server

by fboldo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.0.0

  • Disambiguation5/5

    Each tool produces a distinct output format: PNG preview versus STL export. No overlap in purpose, and both descriptions clearly specify their output.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: render_scad_png and export_scad_stl. The naming clearly indicates the action and target format.

    Tool Count3/5

    At 2 tools, the server is minimal but covers basic rendering/exporting needs. It is slightly thin but not unreasonable for a narrowly scoped utility.

    Completeness3/5

    The server provides a render and an export operation, but lacks common auxiliary functionality such as error checking, previewing in 3D, or accessing model metadata. The core workflow of generating a preview and exporting an STL is covered.

  • Average 3.7/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • 0 of 2 community issues answered or closed in the last 6 months
    • 0 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations provided, the description must disclose behavioral traits, but it only mentions the return format as an 'embedded resource blob'. It does not discuss prerequisites (e.g., OpenSCAD installed), error cases, or any side effects, leaving significant behavioral ambiguity for a tool with no annotation support.

    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 a single, front-loaded sentence that directly states the tool's function and return format. Every word is purposeful and there is no redundant information or filler.

    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 two-parameter tool with a complete schema and output schema available, the description covers the core functionality and return format. It might benefit from a note about the filename being optional or the rendering process, but these are not essential given the schema and output schema richness, making the description reasonably complete.

    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 input schema has 100% coverage with descriptions for both parameters, so the baseline is 3. The description adds minimal semantic value beyond the schema; it implies scadCode usage by mentioning 'OpenSCAD (SCAD) source code' but does not clarify filename defaults or behavior, which the schema already documents.

    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 uses a specific verb 'Export' and identifies both the input (OpenSCAD source) and output (STL), clearly distinguishing this from the sibling tool render_scad_png which produces PNG images. The intent is unambiguous.

    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?

    The description implies usage when an STL file is needed from OpenSCAD code, but it does not explicitly mention the sibling tool or provide when-not-to-use guidance. It gives a clear context but lacks exclusions or alternative tool references, putting it at the implied usage level.

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

  • Behavior3/5

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

    No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool renders to PNG and supports camera control, but does not mention error handling, execution characteristics, or the relationship between cameraPreset and cameraPosition when both are provided. It adds some value over the schema but leaves gaps.

    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, with the main purpose front-loaded in the first sentence and parameter usage summarized efficiently in the second. No unnecessary words or repetition of schema details.

    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 5 parameters including an enum and nested object, the description covers all key inputs (scadCode, width/height, camera options) and states the output as PNG. Since an output schema exists, return values are documented elsewhere. It could mention what happens on invalid code or if both camera options are provided, but overall it is complete enough for a simple render tool.

    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%, so the schema already documents all parameters. The description restates the parameters in prose but does not add new semantic details beyond what the schema provides, such as default values or the precedence rule between cameraPreset and cameraPosition (which is partially in the 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?

    The description clearly states the tool renders OpenSCAD source code into a PNG preview image, using a specific verb ('render') and resource ('SCAD source code'), and distinguishes from the sibling tool by mentioning PNG output (vs STL). This makes the purpose unambiguous.

    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?

    The description explains how to use the tool (provide scadCode, set optional width/height/camera options) but does not explicitly state when to choose this over export_scad_stl or mention any exclusions. The usage context is implied by the word 'preview' but not made explicit.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

openscad-mcp-server MCP server

Copy to your README.md:

Score Badge

openscad-mcp-server MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fboldo/openscad-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server