Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Get accuracy scores

get_scores
Read-only

Fetch community accuracy scores for a CAD model by ID across five dimensions, including average and number of ratings.

Instructions

Community accuracy scores in five dimensions (dimensional, printability, manufacturability, documentation, compatibility): average and number of ratings.

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_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior4/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 genuine value by disclosing the return content (five named dimensions, average plus number of ratings) and implying the data is community-sourced and therefore may be sparse or subjective.

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?

One compact sentence, front-loaded with the resource and followed by the dimension list and return shape; nothing is wasted. The parenthetical enumeration is dense but earns its space since there is no output schema.

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 simple read-only lookup this covers what is returned and the annotations cover safety, but it omits the meaning of model_id and the behavior when a model has no ratings, which are the two things an agent most needs to call it correctly.

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 0% and the description never mentions the single parameter, so nothing explains that model_id identifies which model's scores are fetched or what format it takes. The description does not compensate for the schema 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 names a specific resource (community accuracy scores) and enumerates the five dimensions plus the returned values (average and rating count), so it is far more than a restatement of 'get_scores'. It stops short of saying the scores are for a given model, which is left to the schema.

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?

Usage is implied rather than stated: an agent can infer this is the tool for retrieving quality/accuracy ratings, but there is no explicit 'use when' framing, no note about what to use instead for other model data, and no mention of the no-ratings case.

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