Skip to main content
Glama
liangjunglj-cpu

Almond MCP

publish_objects_to_chestnut

Export selected Rhino objects as a GLB and publish them to Chestnut, with options for physics body type, collider, scale, mass, and linked updates.

Instructions

Exports specific Rhino objects as one GLB and publishes them to Chestnut.

Use this after execute_rhino_script (and optionally validate_structure), passing the returned object GUIDs. Reusing asset_id updates the existing Chestnut asset without changing placements that already reference it.

Args: guids: Rhino object GUIDs to export. Unrelated document objects are excluded. asset_name: Human-readable name shown in Chestnut. asset_id: Stable optional ID for linked updates. Generated deterministically from the Rhino document and GUIDs when omitted. body_type: "static" for architecture, "dynamic" for loose props, or "kinematic" for script-driven objects. collider: Collider intent: "box", "convex", "compound", or "trimesh". Chestnut currently falls back to a box where needed. preserve_scale: Keep Rhino's real-world dimensions instead of normalizing the model to a one-metre display prop. mass: Physics mass in kilograms. Static bodies always use zero. Returns: JSON containing the stable Chestnut asset ID, URL, metadata, and whether the operation created or updated the asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massNo
guidsYes
asset_idNo
colliderNobox
body_typeNostatic
asset_nameYes
preserve_scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description fully discloses behavior: reusing asset_id updates existing asset, excluded unrelated objects, collider fallback, static body mass zero, and deterministic asset_id generation. All key behavioral traits are covered.

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?

Well-structured with bullet points and clear sections, but slightly verbose. Each sentence adds value, though could be more concise.

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?

Given complexity and no annotations, description covers usage, parameters, and return values. Lacks explicit differentiation from siblings and output schema details, but mostly complete.

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

Parameters5/5

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

Schema coverage is 0%, but the description thoroughly explains all 7 parameters including defaults, constraints (e.g., static bodies always zero mass), and intent (e.g., body_type options). Adds significant meaning beyond the schema.

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 clearly states it exports Rhino objects as a GLB and publishes to Chestnut, specifying the verb and resource. However, it doesn't explicitly differentiate from sibling tools like 'publish_to_chestnut', which may also publish to Chestnut but with different parameters.

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

Usage Guidelines4/5

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

Provides clear guidance to use after execute_rhino_script and validate_structure, and explains asset_id reuse. Does not mention when not to use or alternative tools.

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

Install Server

Other Tools

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/liangjunglj-cpu/almond-mcp'

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