Skip to main content
Glama

Axad

Register

show_register
Read-only

Displays one message in a formal and an informal version, for a learner who asks how to say it politely or casually: the changed words are marked, with a note on who gets which.

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": {
      "mean": "<mean>",
      "formal": "<formal>",
      "informal": "<informal>",
      "lang": "<lang>"
    },
    "name": "show_register"
  }
}

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.
meanYes
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
noteNo
formalYes
informalYes

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 and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the output pairs two registers and marks the differing words, and it carries an audience note. It does not explain the fold behavior or how the one-tap next steps behave, so it stops short of full coverage.

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?

It is a single front-loaded sentence that leads with the core action and then qualifies it with the trigger and the rendered detail. The colon-chained clauses make it slightly dense to parse, but every phrase carries information.

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?

Seven parameters with nested formal/informal objects and no output schema is substantial complexity, and the description covers the visible result well. However, it leaves the 'fold' secondary-widget behavior and the 'next' action array unexplained, which an agent needs in order to call the tool correctly.

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 coverage is 43%, below the threshold where the schema alone suffices, so the description must compensate. It does add meaning for 'note' ('a note on who gets which') and gestures at 'marks' ('the changed words are marked'), but says nothing about 'mean', 'fold', or 'next', leaving over half the parameters undocumented 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 gives a specific verb and resource ('Displays one message in a formal and an informal version') plus the rendered artifact ('changed words are marked, with a note on who gets which'). It is clearly distinguishable in spirit from siblings like show_contrast or show_alternatives, though it never names them explicitly.

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

Usage Guidelines4/5

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

It supplies a concrete trigger condition: use when 'a learner asks how to say it politely or casually.' That is a real when-to-use statement rather than an implied one. There are no explicit exclusions or named alternatives, which keeps it below a 5.

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.