Skip to main content
Glama

Polyfork low-poly 3D assets

by dev.polyfork

get_asset

Full detail for one asset: real-world size in metres, triangle count, palette, animatable parts, renders you can open to SEE it, and the correct download URLs for the caller. A model with has_ik true also returns a measured gait or arm block: segment lengths, foot offsets, phase order, step length, reach. That is everything needed to make it walk or reach in any engine, and /cdn/walk.mjs already does it for three.js. If the asset is paid and this connection does not own it, the reply carries the price and a buy link instead: quote both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesasset id, e.g. windmill-3aad49

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral disclosure burden and does so well. It explicitly reveals conditional blocks for has_ik models, the paid/not-owned branch returning price and buy link instead, and caller-specific download URLs. This goes beyond a generic 'get asset' statement and gives the agent an accurate model of response variation.

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 dense but every sentence earns its place: it front-loads the core purpose, then details the standard fields, the IK conditional, and the paid-asset branch. Formatting with backticks aids readability without adding fluff.

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?

Given the low complexity (one required parameter), lack of output schema, and no annotations, the description is remarkably complete. It covers the main return categories, the IK special case, the paid-asset alternate response, and even points to /cdn/walk.mjs for implementation. The only omitted case is an invalid/not-found id, but that is minor against the breadth provided.

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% for the single id parameter and includes an example, so the schema already fully explains the parameter. The description adds no additional parameter-level detail, matching the baseline of 3 for high schema coverage.

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?

Starts with 'Full detail for one asset', a specific verb and resource, then enumerates the concrete data returned: real-world size, triangle count, palette, animatable parts, renders, and caller-specific download URLs. The 'one asset' scope clearly distinguishes it from search/list siblings like search_assets and find_matching.

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?

The description clearly indicates this is for retrieving full detail on a single known asset, and it provides context on conditional reply shapes for IK models and paid assets. However, it does not explicitly contrast with sibling tools such as get_variant or get_kit, nor state when not to use it, so it stops short of full exclusion guidance.

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

All Polyfork low-poly 3D assets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct responsibility: searching the catalogue, inspecting a single asset, expanding into a compatible scene, managing kits, placing objects on terrain, generating variants, previewing scenes, checking ownership, and reporting gaps. Even the meta tools (get_help, report_need, who_am_i) are cleanly separated from the asset-workflow tools.

Naming Consistency4/5

The naming is largely consistent snake_case with an action_noun shape: get_asset, get_kit, get_terrain, list_kits, search_assets, preview_scene. Minor deviations like find_matching and who_am_i still read clearly and do not create confusion.

Tool Count5/5

Eleven tools is a well-scoped count for a 3D asset catalogue server that also handles scene composition, terrain, variants, previews, and account context. Each tool earns its place and none feel redundant or like filler.

Completeness5/5

The surface covers the full workflow from searching and inspecting assets, through variants and kits, to scene placement, terrain height queries, previews, and ownership checks. Meta tools for help and reporting gaps also close the loop, so an agent is unlikely to hit a dead end.

Resources