Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Get a creator

get_creator
Read-only

Retrieve a creator's public profile and models to review their CAD contributions; the donation URL points to a webpage and is not a payment action.

Instructions

A creator's public profile and their models. Donations are made on the website; donate_url is a link to that page, never a payment action.

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": {
      "username": "<username>"
    },
    "name": "get_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

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 safety is covered. The description adds one genuinely useful behavioral clarification, that donate_url is a link and never a payment action, which prevents misinterpretation. It says nothing about pagination behavior, what happens with an unknown username, or how the model list is composed.

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 no filler, and the core purpose is front-loaded. The second sentence is narrow but earns its place as a safety clarification.

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 and 0% schema coverage, the description carries the full burden and does not meet it. An agent is not told what a returned profile or model list looks like, how paging behaves, or how failures for a bad username surface.

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% across three parameters. The description explains no parameter meaning at all: it never says username identifies the creator, nor what limit/offset control or what the defaults and maximums imply. The donate_url sentence describes a response field, not an input, so it does not compensate.

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 and scope: 'A creator's public profile and their models.' That distinguishes it from sibling reads such as get_model or get_company, though it never states the verb or explicitly contrasts with them, so it stops short of 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives like search_companies or get_model. The agent must infer that this is the lookup to use when it already has a username.

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