Mokxi

Search parts

search_parts

Read-onlyIdempotent

Find Mokxi parts by what they are ("temperature sensor", "oled", "motor driver"). Returns each part's type, pins and settings, from the simulator's own catalog, with Mokxi's own picture of the part where mokxi.com has one. Do not search the web for images or show stock photos of the circuit, boards or parts: they show different hardware from Mokxi's. Use only the image URLs Mokxi returns, which are its own drawings.

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

Input Schema

Name	Required	Description	Default
`limit`	No	How many to return, 1 to 30. 10 by default.
`query`	Yes	A few words: what the part is or does, or its chip name.

Output Schema

Name	Required	Description	Default
`note`	No
`parts`	Yes
`presentation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "parts": {
+      "items": {
+        "properties": {
+          "board": {
+            "type": "boolean"
+          },
+          "description": {
+            "type": "string"
+          },
+          "image": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "page": {
+            "type": "string"
+          },
+          "pins": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "props": {
+            "items": {
+              "properties": {
+                "kind": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "options": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "range": {
+                  "type": "string"
+                },
+                "unit": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "name",
+                "kind"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "name",
+          "pins",
+          "props"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "presentation": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "parts"
+  ],
+  "type": "object"
+}

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, closed-world, idempotent, and non-destructive behavior. The description adds valuable provenance: results come from the simulator's own catalog, include type/pins/settings, and images are Mokxi's own drawings only where available. It also explicitly rules out stock photos and web image search, preventing a common misuse.

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?

Front-loads the purpose and return content, then follows with the image constraint. The image warning is slightly repetitive ('do not search the web' plus 'use only image URLs Mokxi returns'), but the overall length is appropriate and every part serves a clear purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read-only search with full input schema and an output schema, the description covers purpose, scope, return fields, and the critical image-provenance caveat. Limit and pagination details are left to the schema, which is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 because query and limit are already documented. The description adds meaning with concrete examples of acceptable query terms ('temperature sensor', 'oled', 'motor driver') and clarifies that returned images must come from Mokxi.

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?

States a specific verb and resource: 'Find Mokxi parts' by what they are, with concrete examples. It also states what is returned (type, pins, settings, Mokxi images). It does not explicitly distinguish from sibling get_part, but the by-description search scope is clear.

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?

Gives clear context for using it when you know what a part is or does, and strongly prohibits searching the web for images. However, it does not name get_part or another alternative for exact-part lookup, so routing guidance versus siblings is incomplete.

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

All Mokxi tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?