Skip to main content
Glama

Get paste-ready source for a catalog item

get_item_source
Read-onlyIdempotent

Free, no account needed. Returns working code that renders one three.ws catalog item on any site: the web component (pinned to the exact published version with its SRI hash), the tag our own browse grids use, plain three.js with GLTFLoader, or a React component. Motion clips return three.js code that parses the clip JSON and plays it. Omit framework to get the one that fits the item; pass all to get every variant at once. Use this when you are ready to put a catalog item on a page or in an app; call get_catalog_item first if you still need its license or metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesCatalog id from search_catalog.
frameworkNoWhich form to emit. Defaults to the recommended one for the item kind. "all" returns every applicable variant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower, and the description still adds real context: free and no account needed, versions pinned with an SRI hash, and special handling where motion clips return clip-parsing playback code. It stops short of describing response size or shape, which keeps it from a 5 given there is no output schema.

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 front-loading is strong: the availability and one-line purpose come first, then the variant list, then the default/'all' rules, then the when-to-use routing. It is dense and long-sentenced, but nearly every clause carries operational information; a slight trim of the parenthetical version/SRI detail would tighten it.

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 two-parameter read-only generator, the description covers what is produced for each option, the default behavior, the special motion-clip case, and the prerequisite alternative. With no output schema and full schema coverage on inputs, nothing an agent needs in order to call this correctly is missing.

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 100%, so baseline would be 3, but the description adds genuine meaning beyond the enum labels by explaining what each variant actually emits and how the omitted-framework default is chosen per item kind. A caller can pick a value from the description alone without knowing what 'agent-3d' versus 'model-viewer' means internally.

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?

The description opens with a specific verb+resource: it returns working code that renders one three.ws catalog item on any site. It then enumerates the four emitted forms (agent-3d, model-viewer, three/GLTFLoader, React) plus the motion-clip special case, which is far more specific than the title alone and clearly distinguishes it from get_catalog_item.

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

Usage Guidelines5/5

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

It states exactly when to call it ('when you are ready to put a catalog item on a page or in an app') and routes to the sibling for the earlier step ('call get_catalog_item first if you still need its license or metadata'). It also explains the default and the 'all' behavior, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.