Skip to main content
Glama
Sign In
Construct

Construct

by rtmandreyev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hologram_compile

Read-onlyIdempotent

Compile a tessera-hologram sheet into tessera-geometry, converting part-based definitions into usable 3D geometry for model building or printing.

Instructions

Compile a tessera-hologram sheet into tessera-geometry.

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": {
      "sheet": "<sheet>"
    },
    "name": "hologram_compile"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the input-to-output transformation, but it does not explain failure behavior for invalid sheets or the nature of the produced geometry beyond its label.

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 with no filler or redundant wording. It communicates the core transformation immediately.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a compilation tool that accepts a nested object and has no output schema, the description is too thin. It does not explain what a valid sheet contains, what the resulting geometry looks like, or how errors are surfaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter is an object with 0% schema description coverage. The description only labels it a 'tessera-hologram sheet,' which adds minimal meaning and does not describe the sheet's required structure, despite the parameter being a nested object.

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 uses a specific verb, 'Compile,' and names both the input and output resources, 'tessera-hologram sheet' and 'tessera-geometry.' It is clearly distinguishable from hologram_validate or hologram_template by its transformation purpose, though it does not explicitly contrast itself with those siblings.

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

Usage Guidelines2/5

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

The definition provides no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is the compilation step after validation or template selection, but nothing in the text states that relationship.

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