Skip to main content
Glama

Axad

Dialogue

show_dialogue
Read-only

Displays a role-play of a real situation, such as calling the doctor or asking the way, for a learner who wants to practise a conversation: 4 to 8 lines where the learner plays B and sees each B line on request.

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": {
      "situation": "<situation>",
      "a": "<a>",
      "b": "<b>",
      "lines": "<lines>",
      "lang": "<lang>"
    },
    "name": "show_dialogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
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.
linesYes
situationYes

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
Behavior4/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 bar is lower, and the description still adds real behavioral detail beyond them: a 4–8 line cap, a fixed learner role (B), and progressive reveal of each B line on request. That reveal-on-demand behavior is not derivable from the schema. It does not cover the fold or next-step behaviors, which the schema carries instead.

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 with the core purpose first and the operative detail after a colon. It is dense but every clause carries information; no filler or restatement of the title.

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?

No output schema exists, so the description must carry the return semantics, and it does reasonably well by describing what the learner sees. However, for a 7-parameter widget with 5 required fields and bare 'a'/'b'/'situation' parameters, an agent still lacks guidance on speaker naming, line content constraints, and the interaction contract.

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%, so the description has to compensate for five required parameters. It partially does: it constrains 'lines' to 4–8 and implies 'a' and 'b' are the two speakers with the learner in slot B, and it motivates 'situation'. But 'situation', 'a' and 'b' have no schema descriptions and gain no format or content guidance from the description, leaving meaningful ambiguity.

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 concrete verb ('Displays') and a specific resource ('a role-play of a real situation') and illustrates it with two examples (calling the doctor, asking the way). It also defines the output shape (4–8 lines, learner plays B, B lines revealed on request), which lets an agent distinguish it from other show_* widgets. It stops short of naming a sibling, so it lands at 4 rather than 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?

Usage is implied through the phrase 'for a learner who wants to practise a conversation', which tells the agent the pedagogical condition for calling it. There is no explicit when-not guidance and no named alternative among the many sibling show_* tools, so the agent must infer selection from the situation 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.