Skip to main content
Glama
Sign In

Mokxi

by com.mokxi
OverviewDiscussionsAdmin

List boards

list_boards
Read-onlyIdempotent

Every microcontroller board Mokxi simulates, all 44 of them, with its type for the "board" field, the code it takes, its pin names, its page on mokxi.com and Mokxi's own picture of it. Report the count and names from this list. Show these images, not web photos of the boards.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
boardsYes
presentationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "boards": {
+      "items": {
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "image": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "page": {
+            "type": "string"
+          },
+          "pins": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "name",
+          "code",
+          "pins"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "presentation": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "boards"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world lookup, so the safety profile is covered. The description goes further by fixing the result set size (44, complete, no filtering), enumerating returned fields, and warning that images are Mokxi's own rather than web photos — a genuine behavioral constraint an agent would otherwise get wrong.

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?

Three sentences, with the identity and scope of the resource front-loaded. The opening sentence is a long run-on and "all 44 of them" slightly repeats "Every ... board," but nothing is wasted overall.

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

Completeness4/5

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

For a zero-parameter list tool with an output schema and full annotation coverage, the description supplies more than enough to call it correctly, including the completeness guarantee and the image-source rule. The only thing missing is any sibling comparison, which is low-stakes here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate on the input side; the baseline of 4 applies. The enumeration of returned fields is output information that the output schema likely already carries.

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: it enumerates every microcontroller board Mokxi simulates (all 44), and it lists exactly which fields come back (type for the "board" field, code, pin names, page URL, image). That is concrete enough to distinguish it from get_part or search_parts, though the description never explicitly draws that contrast.

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?

"Report the count and names from this list. Show these images, not web photos of the boards" is real guidance, but it governs how to present results rather than when to call this tool instead of a sibling. There is no stated precondition or exclusion for selection.

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

All Mokxi toolsInspect
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