Skip to main content
Glama
Sign In
Construct

Construct

by rtmandreyev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

construct_compile

Read-onlyIdempotent

Compile a valid v2 scene or parameter document into construct-geometry v2, or return diagnostics; artwork bytes are not read and slots carry asset ids and hashes only.

Instructions

Compile a valid v2 scene or parameter document into construct-geometry v2 (or return its diagnostics). Artwork bytes are never read: slots carry asset ids and hashes only.

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": {
      "document": "<document>"
    },
    "name": "construct_compile"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesa construct-scene (version 2) or a construct-params document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real context on top: no artwork bytes are ever read, slots carry only asset ids and hashes, so the call is side-effect-free with respect to assets. It also discloses the failure mode returns diagnostics rather than throwing. It does not describe output size or cost for large scenes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and result, followed by the asset-handling caveat. Every clause carries information, though the parenthetical about diagnostics slightly interrupts the main clause flow.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of describing returns, and it only names the output type (construct-geometry v2) without saying what that structure contains or what the diagnostics look like. For a single-input compile tool that is workable but leaves the agent guessing at the response.

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?

Only one parameter and the schema already documents it at 100% coverage as a construct-scene v2 or construct-params document. The description restates that union without adding format, versioning, or required-field detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb (compile) and both accepted input document kinds, plus the output artifact (construct-geometry v2). It does not name a sibling to distinguish itself from the near-identical hologram_compile, so it stops short of full differentiation.

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 phrase "Compile a valid ... document" implies the input must already validate, and "or return its diagnostics" hints at a validation role, but the description never says when to reach for this versus construct_diagnose, hologram_validate, or hologram_compile. Usage is inferable rather than stated.

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