Skip to main content
Glama

afrim_list_schemes

Lists input-method schemes with their languages, key counts, and word lists to help select the right Ethiopian keyboard layout (IDs: am, gez, ethiopic, geezime).

Instructions

List the input-method schemes (keyboard layouts) with their language, number of keys and word lists. Scheme ids: am, gez, ethiopic, geezime.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'List' implies a read-only operation and it discloses the payload fields (language, number of keys, word lists). It says nothing about ordering, size, or whether the id list is exhaustive, which is the main residual gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and its clarifying gloss, followed by the concrete id values. Every clause adds information; nothing is padded.

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 zero-argument list tool with an output schema, this covers what an agent needs: what is listed and what fields come back. The only soft spot is uncertainty about whether the four enumerated ids form a complete set.

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 tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain. The enumerated scheme ids are extra context, though there are no input arguments they could describe.

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?

States a specific verb and resource ('List the input-method schemes (keyboard layouts)') and clarifies the domain term with a parenthetical, so an agent knows exactly what is returned. It does not differentiate itself from siblings like afrim_keystrokes or afrim_lookup, though the resource noun is distinct enough to infer.

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: by enumerating scheme ids the description hints this is the discovery step before other scheme-dependent calls, but it never states when to use this versus afrim_keystrokes or afrim_lookup. No explicit prerequisites or exclusions are given.

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