Skip to main content
Glama

Axad

Contrast

show_contrast
Read-only

Displays two or three look-alike forms side by side, for a learner confused by the difference: one row per side with examples, and a test to tell them apart.

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": {
      "sides": "<sides>",
      "key": "<key>",
      "lang": "<lang>"
    },
    "name": "show_contrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
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.
sidesYes

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.4/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 agent knows this is a safe, closed display action. The description adds the rendered layout (side-by-side rows, one row per side, plus a test), which is genuinely useful beyond the annotations. It says nothing about the folded vs. open widget behavior or the one-tap next steps, though those are covered by schema parameter descriptions.

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 naming the action first, then the audience, then the layout, with no filler. The trailing colon-list is slightly compressed but still readable. Nothing here is wasteful enough to penalize.

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 read-only display widget with no output schema, the description covers what is rendered and why, which is most of what an agent needs. It leaves `key` unexplained and does not connect the described "test to tell them apart" to any field, so the agent cannot tell whether the test is generated or supplied. Adequate but not complete.

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?

With 60% schema description coverage, baseline is around 3. The description usefully conveys that `sides` holds 2-3 entries each carrying an example, and that a distinguishing test accompanies them, which is meaning the schema alone does not spell out. The required `key` parameter is undocumented in both schema and description, leaving a real gap.

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 two or three look-alike forms side by side") and adds the differentiating condition ("for a learner confused by the difference") plus the output shape (one row per side, a test). It does not name a sibling such as show_forms or show_alternatives, so the agent must infer the boundary itself. Clear purpose, but no explicit sibling contrast to raise it to a 5.

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 phrase "for a learner confused by the difference" implies the trigger context, which is more than nothing. However, it never states when not to use it or which sibling to pick instead (e.g. show_forms for a plain paradigm table, show_alternatives for non-confusable options). Usage is implied rather than specified.

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.