Skip to main content
Glama

Axad

Gloss chunks

show_gloss_chunks
Read-only

Displays how a span of the target language is built, for a learner who wants to see it: the text split into chunks, a literal gloss for each word, links between parts that stand apart, and a translation of the span.

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": {
      "text": "<text>",
      "chunks": "<chunks>",
      "translation": "<translation>",
      "lang": "<lang>"
    },
    "name": "show_gloss_chunks"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixNo
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.
textYes
linksNo
chunksYes
widenedNo
structureNo
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / structure
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "clauses": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "kind": {
      +            "type": "string"
      +          },
      +          "parts": {
      +            "items": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "class": {
      +                  "type": "string"
      +                },
      +                "role": {
      +                  "type": "string"
      +                },
      +                "words": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "words",
      +                "role",
      +                "class"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "kind",
      +          "parts"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "clauses"
      +  ],
      +  "type": "object"
      +}
  2. 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"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the output is a rendered multi-part view, but says nothing about selection effects beyond display, why idempotentHint is false for a display tool, or what happens to the supplied inputs.

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 that leads with the verb and then lists the four rendered components; nothing is redundant. It is slightly dense but earns its length by mapping to specific schema fields.

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

Completeness3/5

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

For a 10-parameter tool with nested objects and no output schema, describing the rendered result partially substitutes for a return schema and is genuinely useful. However, several structural parameters (structure, fix, widened) and the folding/secondary-widget behavior are not addressed, which is thin for this complexity.

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 only 30% across 10 parameters, and the description compensates for the most opaque ones by explaining what chunks, per-word glosses, links, and translation represent. It still says nothing about fix, widened, structure, or fold, leaving a substantial share of the nested schema unexplained.

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 ("Displays") and enumerates exactly what is rendered: chunked text, word-level literal glosses, cross-part links, and a span translation. This clearly separates it from narrower siblings like show_structure or show_explain, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers only a vague audience cue ("for a learner who wants to see it") with no when-to-use/when-not guidance and no routing away from adjacent display tools such as show_structure, show_examples, or show_alternatives. The agent must infer the choice from sibling names alone.

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.