get_packRetrieve a free 3D asset pack manifest with direct CDN URLs, licenses, geometry budgets, loader snippets, and a starter scene. Download models individually or use the assembled scene.
Get a free pack manifest with direct CDN URLs, licences, geometry budgets, loader snippets and its assembled starter scene. Download models individually or use the starter scene.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden. It implies a read-only operation (fetching a manifest) without side effects like modification or creation. It does not explicitly state that no data is changed, but the phrasing is clear enough to infer non-destructive behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, front-loaded with the main action, and uses two clear sentences. It avoids unnecessary detail while conveying the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is sufficient for an agent to understand the general function, but it lacks context about what a 'pack' represents and how 'slug' is used. Given the broader set of sibling tools, this missing detail could cause confusion, though the description covers the core action adequately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'slug' is not described in the schema, and the description does not explain what a slug represents or how it should be formatted. The name itself gives some hint, but the description adds no meaningful semantic detail beyond what is already visible from the parameter name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: retrieving a free pack manifest with CDN URLs and related details. It also mentions the alternative usage of downloading models individually or using the starter scene, which provides a clear functional scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly compare this tool to sibling tools like get_asset or search_packs. It implies its use case by describing what it returns, but does not give direct guidance on when to choose it over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.