Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Add images

add_images

Attach up to 10 JPEG, PNG, GIF, or WebP images with optional captions to a user's own model after explicit confirmation.

Instructions

Add pictures to the user's own model. Only after the user's explicit yes.

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>",
      "paths": "<paths>"
    },
    "name": "add_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesJPEG, PNG, GIF or WebP pictures.
captionsNoOne caption per image, or none.
model_idYesThe user's own model (id or page URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false and idempotentHint=false. The description adds the consent gate and the ownership restriction, both real context not present in the structured fields. It does not say whether repeated calls append duplicates, whether there is a per-model image cap, or what happens when a path is invalid.

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?

Two short sentences with zero filler and the consent requirement placed after the action statement. The extreme terseness borders on under-specification, but nothing written is redundant.

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

Completeness3/5

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

For a 3-parameter mutation with full schema coverage, annotations and no output schema, the definition covers the essentials of what it does and the consent condition. It leaves out duplicate handling, failure modes and the ownership requirement beyond 'own model', which an agent calling a write tool would want.

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 coverage is 100%, so paths, captions, model_id and the 10-image limit are already documented in the schema. The description adds only the ownership constraint on model_id. Baseline 3 is correct when the schema carries the parameter burden.

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?

Specific verb ('Add') plus resource ('pictures') and a clear scope restriction ('the user's own model'). It is distinguishable from siblings such as show_images (retrieval) or upload_model (new model creation), though it never names any sibling to sharpen the contrast.

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

Usage Guidelines3/5

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

The line 'Only after the user's explicit yes' is a concrete precondition for invocation, which is more than most definitions offer. However, there is no guidance on choosing this over show_images or upload_version, and no statement about which users/models qualify beyond 'the user's own model'.

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