Polyfork low-poly 3D assets

find_matching

Given one asset, return assets that BELONG IN A SCENE WITH IT: same kit first, then shared palette, then compatible real-world scale, spread across classes so you get a house, a tree and a barrel rather than eight houses. Use this to turn a single pick into a scene. Returns a ready preview URL.

Input Schema

Name	Required	Description
`id`	Yes
`free`	No	only free assets
`limit`	No	default 8, max 30
`compact`	No	shortlisting rows only, as in search_assets, each with its `why`. get_asset has the rest.
`max_triangles`	No	triangle budget ceiling; applies to the preview scene as well
`min_triangles`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / compact

Added value: +{
+  "description": "shortlisting rows only, as in search_assets, each with its `why`. get_asset has the rest.",
+  "type": "boolean"
+}

First observedAug 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose non-obvious traits: prioritized ordering (kit > palette > scale), deliberate class diversification, and that the response includes a ready preview URL. It does not cover cost, auth, or failure behavior, but the ranking and diversification semantics are the traits an agent most needs.

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?

Two sentences, zero filler, and the core behavior (what it returns and in what order) is front-loaded before the usage cue and the return note. The density is justified by the ranking rules it conveys.

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?

For a 6-parameter tool with no annotations and no output schema, the description covers the conceptual model and return shape reasonably but leaves a real gap around the compact/full row distinction, default and max limit, and triangle-budget behavior – all of which change what the agent receives.

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?

Schema coverage is 67%, so roughly a third of parameters rely on inference, and the description adds no meaning about any parameter – not 'compact', not 'limit', not the triangle bounds, and not the 'free' filter. The only return hint ('ready preview URL') is about output, not inputs.

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 and resource ('Given one asset, return assets that BELONG IN A SCENE WITH IT') and goes further to spell out the ranking logic: same kit, then palette, then scale, spread across classes. An agent can distinguish it in spirit from search_assets (query-driven) without opening schemas, though no sibling is named outright.

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 a clear triggering context: 'Use this to turn a single pick into a scene,' which tells the agent this is a follow-on to selecting one asset. No explicit 'do not use when' or named alternative such as search_assets, so it falls short of a 5.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?