Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_thumbnail

Read-only

Generates a preview image from a search hit thumbnail key or asset URL, helping identify and verify USD assets before use.

Instructions

Return a preview by search hit thumbnail_image_key or asset URL.

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": "asset_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
asset_urlNo
image_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the call yields a preview rather than asset metadata, but it never says what the preview comes back as (image bytes, URL, base64) or what happens when the key is stale or the URL is external. Useful but thin context beyond the annotations.

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?

A single front-loaded sentence with no filler, sized appropriately for a preview helper. The wording 'search hit thumbnail_image_key' is slightly compressed and could be clearer without getting longer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, three undocumented parameters, and an open-world network fetch, the description should explain the return payload and the offset/selection semantics. It leaves the agent guessing at the response shape and how to combine the two asset identifiers.

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 0%, so the description must carry all parameter meaning, and it only loosely names two of the three (image_key, asset_url). The 'offset' parameter is never mentioned, and there is no statement of precedence when both image_key and asset_url are supplied, nor of the empty-string/null defaults.

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 output ('Return a preview') plus the two inputs that identify the asset, which is enough to separate it from asset_inspect or asset_search. It stops short of explicitly positioning itself against those siblings, so a 4 rather than a 5.

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 phrase 'search hit thumbnail_image_key' weakly implies use after a search result, but there is no explicit when-to-use, no when-not-to-use, and no named alternative such as asset_inspect for full-resolution inspection. Guidance is inferred, not stated.

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