Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Show model images

show_images
Read-only

Display a model's preview thumbnail and gallery inline, downscaled to 1024 px, so users can view a part without downloading files.

Instructions

Show a model's preview pictures (thumbnail and gallery) inline, downscaled to at most 1024 px. Use it when the user wants to see a part. Never uses a download.

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": {
      "model_id": "<model_id>"
    },
    "name": "show_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost images to return.
model_idYesThe model's id (uuid) or page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail beyond that — images are rendered inline rather than saved, and are downscaled to a 1024 px cap — but it does not say what happens when a model has no images or how many are returned by default.

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?

Three short sentences with the core purpose front-loaded and the constraints following in priority order. Minor waste in the vague phrase 'see a part', which is less precise than the rest of the description.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing results and does so adequately by naming the returned image types and their downscaled inline form. The absence of empty-result or error behavior is the only meaningful gap for this simple two-parameter read tool.

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?

Schema description coverage is 100%, with both model_id (uuid or page URL) and limit (default 4, max 8) documented in the schema itself. The description's mention of 'thumbnail and gallery' hints at what the limit spans but adds no binding, format, or default information beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource — 'Show a model's preview pictures (thumbnail and gallery) inline, downscaled to at most 1024 px' — with concrete rendering constraints. It implicitly separates itself from the download-oriented siblings by stating 'Never uses a download', though it never names an alternative tool 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?

'Use it when the user wants to see a part' supplies an explicit trigger condition, and the closing note rules out the download path, which is the main adjacent temptation among the siblings. It stops short of naming check_download or download_file as the correct alternative when the user does want a file.

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