brickem-mcp-server

Search Minifigures

search_minifigures

Find LEGO minifigures by name or theme with price information. Search 18,000+ minifigs using partial names to identify characters and check market values.

Instructions

Fuzzy search LEGO minifigures by name with optional theme filter. Returns top 10 matches with prices. Good for finding minifigures when you only know part of the name.

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": {
      "query": "<query>"
    },
    "name": "search_minifigures"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search keywords (name, character, series)
`theme`	No	Optional theme filter, e.g. 'star wars', 'harry potter', 'marvel', 'ninjago'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: fuzzy matching, optional theme filtering, returns top 10 matches with prices. However, it doesn't mention important details like pagination, error conditions, rate limits, or authentication requirements that would be valuable for an agent.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core functionality, the second provides crucial usage context. No wasted words, well-structured and 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?

For a search tool with no annotations and no output schema, the description provides adequate but incomplete context. It explains what the tool does and when to use it, but lacks details about the return format beyond 'top 10 matches with prices' - no information about data structure, error handling, or system constraints.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'fuzzy search' which clarifies the query behavior, but doesn't provide additional parameter semantics beyond what's in the schema descriptions.

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 tool's purpose with specific verbs ('fuzzy search', 'returns') and resource ('LEGO minifigures'). It distinguishes from siblings by specifying it's for when you 'only know part of the name' rather than exact identification or theme-specific listing.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('when you only know part of the name'), which implicitly differentiates it from tools like 'identify_minifigure' or 'lookup_minifigure' that likely require more precise information. However, it doesn't explicitly state when NOT to use it or name specific alternatives.

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

Deploy Server