Keyboardino

Compare layouts

compare_layouts

Read-onlyIdempotent

Compares two keyboard layouts and returns the keys that type different characters. Adds the website's example-text counts of home-row use and same-finger letter pairs for each. QWERTY and Dvorak without names.

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": "compare_layouts"
  }
}

Input Schema

Name	Required	Description	Default
`first`	No	First layout name, such as QWERTY, AZERTY, Dvorak or Colemak. QWERTY without it.
`second`	No	Second layout name, such as QWERTY, AZERTY, Dvorak or Colemak. Dvorak without it.

Output Schema

Name	Required	Description	Default
`item`	Yes
`view`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read, so the bar is low. The description adds real context beyond them: the comparison is character-level ('keys that type different characters') and the result is augmented with example-text home-row and same-finger-pair counts, which an agent could not predict from the annotations.

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 short sentences, front-loaded with the core behavior and the return content. The trailing defaults sentence is terse and slightly clipped ('QWERTY and Dvorak without names'), but nothing is wasted.

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 two-optional-parameter read tool with a full output schema and complete annotations, the description covers purpose, output shape, and defaults. The only gap is guidance on choosing it over a single-layout lookup.

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 description coverage is 100%, so both parameters are already documented, including examples. The description only restates the defaults ('QWERTY and Dvorak without names'), which adds no new meaning beyond the schema. 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 resource ('compares two keyboard layouts') and, crucially, what it returns: the keys that type different characters. That output scope separates it from a plain layout lookup such as get_layout without needing a sibling callout.

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 implied by the description's comparative nature, but there is no explicit when-to-use framing and no mention of when a single-layout lookup (get_layout) would be the better choice. The agent must infer the routing decision.

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

All Keyboardino 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.