Skip to main content
Glama

Axad

Axad menu

show_home
Read-only

Displays Axad's start menu as a list of taps: go on with the open lesson, start a lesson, paste a sentence, inburgering practice, review cards, the bag. Signed in, it says how many cards are due and which lesson is open.

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

Input Schema

NameRequiredDescriptionDefault
langNoBCP 47 code of the language to learn: "nl" (the default).
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare a safe, non-destructive, closed-world read, so the bar is lower. The description still earns credit for disclosing state-dependent output (due card count and open lesson only appear when signed in), which the annotations do not convey. It does not say how the taps behave or how the `next` overrides interact with the default menu, leaving a moderate gap.

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 sentences, no waste, with the core verb and resource front-loaded before the enumerative detail. The tap list is informative rather than redundant and the conditional signed-in behavior is placed last, which suits its secondary importance.

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, no-output-schema, read-only tool, the description conveys the returned shape (a list of taps) and its conditional variation. A small gap remains around the `next` parameter's effect and how the menu differs by language, but completeness is otherwise solid.

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 `lang` and `next` are fully documented in the schema, and the baseline is 3. The description adds nothing beyond the schema about the parameters, notably never mentioning that extra one-tap next steps can be injected or that a language code can be passed.

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 concrete verb and resource: "Displays Axad's start menu as a list of taps," then enumerates the taps so an agent can recognize the home/menu surface. It stops short of naming how it differs from close siblings like show_next or next_step, but the menu framing is specific enough to disambiguate in practice.

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?

The guidance is implied rather than stated: "start menu" plus the signed-in note suggests calling it to present the entry point. There is no explicit when-to-use clause, no exclusion of alternatives such as show_next or show_review, and no note on prerequisites like authentication beyond the passing mention of "Signed in."

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.