ConsoleMouse profiles

Build a ConsoleMouse import code

profile_import_code

Read-onlyIdempotent

Checks a derived ConsoleMouse profile and returns an import code (CMP2) the person pastes into ConsoleMouse under Games > Import profile or in the AI Workshop (Import code), with the plain-language preview and the import steps. A full profile is accepted when base_profile_id names its base. Use format CM1 only when the person has an older ConsoleMouse (0.3.9 to 0.4.x). Read-only: the code is computed and returned, nothing is stored or sent anywhere.

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": {
      "profile": "<profile>"
    },
    "name": "profile_import_code"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the preview and the import steps.	en
`format`	No	CMP2 (default, current ConsoleMouse). CM1 only for ConsoleMouse 0.3.9 to 0.4.x, which need the exact base version.	CMP2
`profile`	Yes	The profile as a JSON object, as JSON text, an import envelope, or an import code (CMP2., or the older CM1.). Usually a derived profile (origin "derived", base_profile_id, patch).
`author_note`	No	Optional note shown with the import preview. Plain text (no control characters); describe the controls, nothing personal.
`base_profile_id`	No	Only for a full profile: the base it was made from.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world, and the description reinforces this with "nothing is stored or sent anywhere" while adding genuinely new information: the response includes the plain-language preview and import steps. It does not describe failure behavior for an invalid profile, which is the remaining gap.

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-loaded with the purpose and deliverable, then the version constraint, then the safety note. Four sentences, all informative, with only mild redundancy between the read-only clause and the readOnlyHint annotation.

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?

With no output schema, the description carries the return-value burden and does so: import code, localized preview, and import steps. Combined with the 100%-covered input schema and safety annotations, an agent has enough to call this correctly.

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 the baseline is 3. The description's format guidance and base_profile_id rule largely restate the schema's own parameter descriptions rather than adding syntax or edge-case meaning (e.g. what happens when an envelope already carries a base id).

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?

Specific verb+resource+deliverable: "Checks a derived ConsoleMouse profile and returns an import code (CMP2)", plus where the code gets pasted. It implicitly separates itself from profile_validate by naming the artifact it produces, but never names a sibling tool explicitly.

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?

Gives concrete selection rules: default CMP2, CM1 only for ConsoleMouse 0.3.9–0.4.x, and that a full profile is accepted when base_profile_id names its base. No exclusions relative to profile_validate/format_spec, so an agent must still infer that boundary.

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

All ConsoleMouse profiles 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?