Assets for three.js

List model packs and prices

list_packs

Read-onlyIdempotent

The packs on sale at Assets for three.js, grouped by shelf: each pack's summary, number of component models and assemblies, how many of its models embed textures, triangle range, price in GBP (VAT included) and USD (tax-exclusive, US edition), page and buy link. Also the shelf bundles, the lifetime licence and the free starter pack. It does not sell, reserve or check stock of anything. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_packs"
  }
}

Input Schema

Name	Required	Description	Default
`shelf`	No	Optional: one shelf id, e.g. "london-housing", "building-sites", "london-high-streets", "london-architecture", "parks-play-sport".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context about scope and return content, including grouped shelf listings, bundles, the lifetime licence, the free starter pack, and the fact that it does not transact or check stock.

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?

The definition is front-loaded with the resource and purpose, then enumerates the returned information efficiently. It is dense but not padded, though the first sentence is long and carries a heavy list of fields.

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?

For a one-optional-parameter read-only listing tool with no output schema, the description sufficiently explains what is returned, including prices, currency treatment, pack contents, bundles, licence, and free starter pack. It also clarifies that no stock or purchase operation occurs.

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?

The single optional shelf parameter is fully documented in the schema with example shelf ids at 100% description coverage. The description does not add filtering semantics beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: listing packs on sale at Assets for three.js, grouped by shelf, with prices and pack contents. It is clear and distinguishable from a single-model lookup, but it does not explicitly name or contrast with siblings such as search_models or get_model.

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

Usage Guidelines2/5

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

The description implies browsing pack listings and prices, but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives. The line that it does not sell or reserve is behavioral, not usage guidance.

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

All Assets for three.js 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?