Skip to main content
Glama

Axad

Scene

show_scene
Read-only

Displays one library picture of a place or situation with its 3 to 6 key words beside it, for a learner who wants the vocabulary of a waiting room, a pharmacy or a kitchen.

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": {
      "image": "<image>",
      "title": "<title>",
      "means": "<means>",
      "words": "<words>",
      "lang": "<lang>"
    },
    "name": "show_scene"
  }
}

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.
imageYes
meansYes
titleYes
wordsYes

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, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds one genuinely new behavioral constraint not present in the schema: the picture must carry 3 to 6 key words. It says nothing about the widget being saved, the fold behavior, or the one-tap next steps, so behavior beyond annotations is only partially disclosed.

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 resource first and the audience qualifier second; there is no filler. It could be tightened slightly, but nothing is wasted.

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 7-parameter widget-composition tool with no output schema and 43% schema coverage, the description explains the core visual contract but leaves the composition (title, means, next buttons, fold) undocumented. An agent can call it, but only by reading the schema closely.

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 schema description coverage at 43%, the description must compensate, and it does so only partially: 'one library picture' clarifies image and '3 to 6 key words' adds a constraint the words array schema lacks. The four undescribed parameters (title, means, and the nested say/means items) and the annotated fold/next/lang behavior receive no elaboration in the description.

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 specific verb and resource: 'Displays one library picture of a place or situation with its 3 to 6 key words beside it.' That is enough for an agent to know it renders a vocabulary scene card. It does not, however, differentiate itself from siblings like show_picture or show_visual, which an agent would have to disambiguate on its own.

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 wants the vocabulary of a waiting room, a pharmacy or a kitchen' implies the use case (concrete everyday-place vocabulary) but never states when to prefer this over show_picture, show_visual or show_examples. No exclusions or prerequisites are given, so guidance is only implied.

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.