Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lego_set_parts

Retrieve the complete parts list for any LEGO set by providing its set number. Get detailed inventory of each brick and element in the set.

Instructions

Get the parts list for a LEGO set.

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": {
      "set_num": "<set_num>"
    },
    "name": "lego_set_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
set_numYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided. The description only states the purpose ('get the parts list') without disclosing behavioral traits such as whether authentication (api_key) is required, rate limits, or what happens on invalid set_num. For a read operation, the description adds no extra behavioral context.

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?

The description is a single, concise sentence of 8 words. It is front-loaded with the verb and resource, making it easy to scan and understand quickly. No extraneous information.

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?

Given no output schema and a list endpoint, the description does not specify the return format, pagination, or how to handle errors. Sibling tools like 'lego_get_set' may provide more context, but the description alone is incomplete for an agent to use effectively.

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 does not explain the parameters. While 'set_num' is likely the set number and 'api_key' an authentication key, the description adds no meaning beyond the schema. For a minimal description, this is insufficient to compensate for the lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('get') and the resource ('parts list for a LEGO set'), which is specific. It distinguishes from sibling tools like 'lego_get_set' (set details) and 'lego_search_parts' (search parts) by focusing on a specific set's parts list.

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?

No guidance on when to use this tool versus alternatives like 'lego_search_parts' or 'lego_get_set'. Agents have to infer from the description alone, which lacks any when-to-use or when-not-to-use information.

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

Deploy Server

Other Tools