Skip to main content
Glama

Axad

Pattern

show_pattern
Read-only

Displays a reusable sentence frame with slots, the fillers that fit each slot, and sentences built from it, for a learner who met a pattern they can use with other words.

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": {
      "frame": "<frame>",
      "mean": "<mean>",
      "slots": "<slots>",
      "built": "<built>",
      "lang": "<lang>"
    },
    "name": "show_pattern"
  }
}

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.
builtYes
frameYes
slotsYes

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

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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false, idempotentHint=false), and "displays" is consistent with them. Beyond that, the description adds nothing about rendering, how the fold and next-step parameters change the reply, or why a pure display tool is non-idempotent — all of which an agent would want to know.

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?

One sentence that front-loads the resource and enumerates its parts, with no boilerplate. The closing learner-context clause is slightly wordy and mildly redundant with the opening, but it does carry usage information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters, five required, 43% schema coverage and no output schema, the description should carry more weight. It leaves fold (a widget-placement flag that materially changes the reply) and next (one-tap follow-ups) entirely unexplained, which is a real gap for an agent constructing a call.

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?

The description clarifies the three content-bearing parameters conceptually: frame (the sentence frame), slots plus fillers (the fillers that fit each slot), and built (sentences built from it). It says nothing about lang, mean, fold, or next, and schema coverage is only 43%, so the meaning of roughly half the parameters is left to the schema's terse strings.

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?

"Displays a reusable sentence frame with slots, the fillers that fit each slot, and sentences built from it" gives a concrete verb plus the exact content payload (frame, slots, fillers, built sentences), so an agent knows precisely what widget comes back. It stops short of differentiating itself from the similarly named sibling show_sentence_frame, leaving an overlap the agent must guess at.

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 trailing clause "for a learner who met a pattern they can use with other words" implies a trigger condition (the learner has just encountered a productive pattern), which is genuine usage guidance. There are no when-not conditions and no mention of alternatives such as show_examples, show_drill, or show_sentence_frame for adjacent teaching needs.

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.