Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

keyboard_layout

Get a visual reference of keyboard key positions and characters for US, UK, German, French, Spanish, or Italian layouts.

Instructions

Get keyboard layout reference showing key positions and characters.

Parameters:
    layout — Layout: 'us' (default), 'uk', 'de', 'fr', 'es', 'it'.

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

Input Schema

NameRequiredDescriptionDefault
layoutNous

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It discloses the purpose and parameter values but does not mention any behavioral traits such as idempotency, caching, error handling, or required network access. The description is lacking in this dimension.

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?

The description is concise with a single clear sentence followed by a parameter list. It is well-structured and front-loaded, though the parameter list could be integrated more seamlessly.

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 simple tool with one parameter and an output schema, the description provides the necessary information: purpose and allowed parameter values. It could elaborate on what the output contains, but it is largely complete given the tool's scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only shows the 'layout' parameter with a default but no enum values. The description adds meaningful detail by listing allowed layout values: 'us', 'uk', 'de', 'fr', 'es', 'it'. This compensates for the 0% schema description coverage.

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?

Clearly states 'Get keyboard layout reference showing key positions and characters.' The verb 'Get' and resource 'keyboard layout reference' are specific, and no sibling tool appears to have similar functionality, distinguishing it well.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for retrieving keyboard layouts, but it does not address alternatives or exclusion criteria.

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