Skip to main content
Glama

Axad

Alternatives

show_alternatives
Read-only

Displays other ways to say the same thing, for a learner who wants to sound more natural or find a simpler form: the original and 2 to 5 alternatives, each tagged by kind, such as simpler or more formal.

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": {
      "original": "<original>",
      "items": "<items>",
      "lang": "<lang>"
    },
    "name": "show_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
glossNo
itemsYes
originalYes

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real value by describing the payload shape — the original plus 2 to 5 alternatives each tagged by kind — which matters because there is no output schema. It says nothing about the fold/next widget mechanics, but the schema covers those.

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?

One front-loaded sentence with a colon that moves straight from purpose to result structure. Every clause carries information; the only slight softness is the informal "sound more natural" phrasing, which is still doing guidance work.

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 read-only display widget with no output schema, the description adequately conveys what the caller gets back and roughly how many items. Gaps are minor: the vocabulary of allowed tags and the role of `gloss` are not stated, but nothing would prevent correct invocation.

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?

At 50% schema coverage, the description compensates for the undocumented `original` and `items` parameters by explaining that the original is echoed and that alternatives are tagged by kind. It also adds a cardinality constraint of 2 to 5 that the schema does not enforce. The `gloss` parameter remains unexplained in both places.

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?

The description pairs a specific verb ("Displays") with a clear resource ("other ways to say the same thing" plus the original and tagged alternatives), so an agent can identify this as a paraphrase/alternatives widget. It does not explicitly distinguish itself from the nearby show_register or show_examples siblings, even though "more formal" tagging overlaps with register.

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?

It gives a motivating use case ("a learner who wants to sound more natural or find a simpler form"), which implies when to reach for this tool. There is no explicit when-not guidance and no sibling is named as an alternative, so the routing decision is only partly supported.

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.