Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Read comments

get_comments
Read-only

Retrieve comments and one-level replies for a model, with pagination and ordering controls, to review community feedback before evaluating or downloading CAD parts.

Instructions

Comments on a model, threaded one level deep. Removed comments show as removed. Read-only: to comment, the user goes to the model page.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNonewest
offsetNo
repliesNoMost replies to include per comment.
model_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds genuine behavioral context beyond them: one-level thread nesting and the fact that deleted comments surface as tombstones rather than disappearing, which changes how results should be interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, each carrying a distinct fact: the threading model and the read-only boundary. Nothing is repeated from the schema or annotations and the constraints are front-loaded.

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?

No output schema exists, and the description never sketches what a comment record contains or how pagination behaves, which matters for a five-parameter paginated read. With annotations covering read-only semantics, this is adequate but leaves real gaps for an agent that must page and order results.

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 description coverage is only 20% — only 'replies' carries a description, while limit, offset, order, and model_id are bare titles. The description adds no meaning for any of these, not even that model_id is the required anchor or that limit caps at 50, so it fails to compensate for the coverage gap.

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 identifies the resource clearly: comments on a model, with the specific structural detail that they are threaded one level deep. The verb is implied by the title 'Read comments' rather than stated, and no sibling tool is named for contrast, but an agent can tell this returns comment data rather than model metadata or scores.

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 'to comment, the user goes to the model page' usefully rules out a write use case, which is the main mis-invocation risk. However, there is no guidance on when to reach for this versus other read tools, nor on how to page through large comment sets with limit/offset/order.

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