ConsoleMouse profiles

Describe a ConsoleMouse profile in plain words

profile_describe

Read-onlyIdempotent

Returns a plain-language preview of a valid ConsoleMouse profile: for a derived profile one sentence per change against its base (keys, macros, press once, mouse movement), for a full profile one sentence per key. Languages: de, en, es, fr, it, pl, pt-BR. Read-only.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the sentences.	en
`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).

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 readOnlyHint, idempotentHint and destructiveHint, so the description's trailing 'Read-only' is redundant rather than additive. The genuinely useful context is behavioral output disclosure: one sentence per change against the base for derived profiles versus one sentence per key for full profiles, plus the precondition that the input must be a valid profile.

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?

A single front-loaded sentence that leads with the verb and resource, followed by the two output modes. It is dense but readable; the embedded language list and the 'Read-only' tail repeat structured data and could be dropped.

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 burden of describing returns and does so for both profile kinds, in addition to naming supported languages and the validity precondition. Nothing an agent needs in order to call this read-only preview correctly is missing.

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, and the description's language list merely repeats the 'lang' enum. It does reinforce that 'profile' accepts a derived profile, but the schema already says this ('origin derived, base_profile_id, patch'), so it adds little beyond the structured fields.

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 resource ('Returns a plain-language preview of a valid ConsoleMouse profile') and immediately defines the output shape per profile kind (one sentence per change vs. one sentence per key). That is enough for an agent to separate it from profile_validate or format_examples without opening any schema.

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?

Usage is only implied: the phrase 'valid ConsoleMouse profile' hints that validation should precede a call, and the derived-vs-full split tells the agent which output to expect, but there is no explicit when-to-use or when-not-to-use guidance relative to profile_validate or profile_import_code.

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?