Skip to main content
Glama
Sign In
hlplanet-mcp

hlplanet-mcp

Official
by hlplanet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Which keyboard sizes have a key

which_sizes_have_key
Read-onlyIdempotent

Identify which keyboard sizes physically include a specific key or key group, and find out which sizes only reach it through an Fn layer.

Instructions

Check which keyboard sizes have a key or key group, e.g. "Delete", "F5", "Insert", "Print Screen", "backtick", "arrow keys", "numpad", "function keys". Sizes without it usually reach it through an Fn layer.

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": {
      "key": "<key>"
    },
    "name": "which_sizes_have_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoNoUse the ISO layout (UK/EU)
keyYesA key name or group: "Delete", "F12", "Home", "arrow keys", "numpad"...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine domain context beyond the annotations: that results can be negative and that absent keys are typically accessed via an Fn layer, which shapes how an agent should interpret the answer.

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?

Two sentences, front-loaded with the core question; the example list is somewhat long but functional and earns its place by clarifying valid key inputs. No wasted preamble.

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 read-only query with no output schema, the description is nearly complete: it explains intent, input domain, and the Fn-layer nuance. It could say more about the return shape (a list of size names), but that is a minor gap against annotations that already carry the behavioral profile.

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 (key, iso) are already documented in the schema. The description's example list enriches the 'key' semantic range but largely overlaps the schema's own examples, so it adds only marginal value above the baseline.

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 ('Check which keyboard sizes have') and resource ('a key or key group'), with concrete examples of the key domain. An agent can distinguish this from list_keyboard_sizes or compare_keyboards without opening the schema.

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?

The description gives clear context for when this tool applies (querying key/group availability across sizes) and adds a helpful caveat that missing sizes 'usually reach it through an Fn layer.' It does not, however, name a sibling or explicitly state when not to use it.

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

Deploy Server

Other Tools