Skip to main content
Glama
Sign In

Mokxi

by com.mokxi
OverviewDiscussionsAdmin

Make a link from code

create_code_link
Read-onlyIdempotent

Make a link that opens a sketch in the Mokxi editor, for code with no circuit worked out: Mokxi reads the sketch, picks the board when none is given and places and wires the parts the code names. Nothing is checked here, so prefer create_project when the wiring matters. Always give the person the link, whole and unchanged.

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": {
      "code": "<code>"
    },
    "name": "create_code_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe whole sketch, 24 thousand characters at most.
boardNoThe board to open it on, such as "uno", "esp32" or "pico". Left out, Mokxi picks one from the code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context: Mokxi auto-selects a board when omitted, auto-places and wires the named parts, and performs no validation. It also gives output-handling guidance ('give the person the link, whole and unchanged'), which is not derivable from annotations. It stops short of describing link lifetime or failure behavior.

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, front-loaded with the purpose, then the caveat, then the output instruction; no filler. The final sentence is slightly emphatic in tone but does carry actionable output-handling information, so it earns its place.

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?

With only two well-documented parameters and no output schema, the description covers what the tool does, when to prefer the alternative, and what the caller should do with the returned link. Minor gaps remain on link lifetime or whether regeneration is expected, but nothing blocks a correct invocation.

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 coverage is 100%, so both parameters are already documented, including the 24k character cap and the board fallback behavior. The description restates the board-defaulting rule but adds no syntax, format, or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and artifact ('make a link that opens a sketch in the Mokxi editor') and scopes it precisely to 'code with no circuit worked out'. That scope clause alone distinguishes it from create_project, which the description then names explicitly.

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

Usage Guidelines5/5

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

Gives both a positive condition ('for code with no circuit worked out') and an explicit alternative with its selecting condition ('prefer create_project when the wiring matters'). An agent has a clear routing rule without needing to inspect sibling schemas.

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