Skip to main content
Glama

Axad

Visual

show_visual
Read-only

Displays a chart for a learner who needs to see how things relate: a verb grid across tenses, a time line, a sentence tree or a topic map.

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": {
      "title": "<title>",
      "chart": "<chart>",
      "lang": "<lang>"
    },
    "name": "show_visual"
  }
}

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.
noteNo
chartYes
titleYes

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the agent knows the safety profile without the description. The description adds that output is a rendered visual for the learner, but says nothing about the reply-widget lifecycle (fold state, one-tap next steps) or why idempotentHint is false for a display operation. With annotations carrying safety, a 3 is right — some added context, no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the verb and resource, then a colon list where every item adds a distinct chart type. No filler, no restatement of the title 'Visual', and the most decision-relevant content comes first.

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 6-parameter tool whose chart parameter is a four-branch discriminated union with nested required fields, the description is thin: it names the variants but does not help an agent decide which variant fits a given teaching goal, nor does it cover the reply-widget mechanics implied by fold and next. With no output schema, the description should say more about what the learner actually sees. Adequate, but with clear gaps.

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?

Schema coverage is 50%, so the description must compensate, and it does for the hardest parameter: the chart anyOf, whose four variants are translated into real pedagogical artifacts (a verb grid across tenses, a time line, a sentence tree, a topic map). That gives more meaning than the bare const strings. It still says nothing about title, lang, note, or the next/fold affordances, so the compensation is partial rather than complete.

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 a chart') plus the resource and enumerates the four chart shapes — verb grid, time line, sentence tree, topic map — which map onto the schema's const values (verbs/timeline/tree/map). That makes the tool distinguishable from siblings like show_picture or show_pattern in kind. It stops short of naming any sibling to contrast with, so an agent must infer the boundary itself.

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 who needs to see how things relate' gives an implied usage condition (relational/spatial content rather than prose explanation). However, there is no explicit when-not guidance and no named alternative such as show_explain or show_picture for cases where a chart is the wrong vehicle. Usage is suggested, not prescribed.

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.