Skip to main content
Glama

Axad

Forms

show_forms
Read-only

Displays the forms of one word as a table, for a learner who asks about them: verb conjugation, article or gender, plural, comparative or diminutive.

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": {
      "lemma": "<lemma>",
      "pos": "<pos>",
      "table": "<table>",
      "lang": "<lang>"
    },
    "name": "show_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
foldNotrue: a secondary widget of this reply, made now and shown folded: only its title row, until one click opens it. Omit it on the reply's main widgets, which show open.
langYesBCP 47 code of the language the widget teaches: "nl". The view speaks and saves its words in it.
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
noteNo
glossNo
lemmaYes
tableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Up to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.",
      +  "items": {
      +    "properties": {
      +      "ask": {
      +        "description": "The message a tap sends, in the learner's words.",
      +        "maxLength": 300,
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "The button's text.",
      +        "maxLength": 32,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label",
      +      "ask"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that output is rendered as a table, which is useful, but it never mentions the widget mechanics available in the schema (fold, next-step buttons, note/gloss) or what happens to unrelated params. It also does not explain that idempotentHint=false is deliberate because each reply builds a fresh widget.

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?

A single front-loaded sentence with zero padding; the colon-delimited list is dense but efficient. Slightly overpacked for one sentence but nothing extraneous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex widget-building tool with 8 params (4 required), nested objects, and no output schema, yet the definition is one sentence that ignores interaction features such as folded secondary widgets and one-tap next steps. An agent would have to reverse-engineer the tool's role in a reply from the schema alone.

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

Parameters2/5

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

With 8 parameters and only 38% schema description coverage, the description must compensate and does not. Only lemma ("one word") and table ("as a table") are indirectly implied; pos, note, and gloss are never explained in either place, and the required pos parameter's accepted values are nowhere documented.

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 ("Displays") and resource ("the forms of one word as a table") and enumerates the form types covered — verb conjugation, article/gender, plural, comparative, diminutive. This is concrete enough for an agent to distinguish it from siblings like show_alternatives or show_correction, though no sibling is named explicitly.

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?

"for a learner who asks about them" gives an implied trigger condition, but there is no explicit when-to-use versus alternatives, no prerequisites, and no exclusions (e.g. when to prefer show_alternatives for synonyms or show_pattern for paradigms).

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.