Skip to main content
Glama

Axad

Sentence frame

show_sentence_frame
Read-only

Displays one sentence split into the places its words take, for a learner who asks about word order: slots such as subject and verbs, the verb places marked, and a note on the rule.

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": {
      "say": "<say>",
      "mean": "<mean>",
      "slots": "<slots>",
      "lang": "<lang>"
    },
    "name": "show_sentence_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
sayYes
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.
noteNo
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.1/5.0
Behavior3/5

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

Annotations already declare this a non-destructive, non-open-world read, so the safety profile is covered. The description adds that the output is a structured visual breakdown with marked verb slots plus a rule note, which helps an agent predict the rendered result, but it says nothing about how the widget relates to the supplied sentence, meaning, or follow-up buttons.

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?

It is a single front-loaded sentence with no filler or repetition. The colon-separated enumeration of what gets shown is efficient, though the inverted phrasing 'the places its words take' costs a little parsing effort.

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?

For a seven-parameter widget tool with no output schema, the description covers only the visual shape and two of the inputs. An agent still does not know what 'say' and 'mean' contribute to the frame or that 'next' adds follow-up chips, which is a meaningful gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 43% across seven parameters, so the description needs to compensate and largely does not. It sheds light on 'slots' (name, verb flag, words) and 'note', but 'say', 'mean', 'lang', 'fold', and 'next' receive no explanation of their role in the rendered frame.

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 names a specific verb and resource — it displays one sentence split into slots such as subject and verb, with verb places marked and a note on the rule. That is concrete enough to distinguish it from generic siblings like show_explain or show_pattern, though the phrasing 'the places its words take' is more literary than precise.

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?

It gives an implied trigger — 'for a learner who asks about word order' — which is genuine context for when to reach for it. However, it names no alternative and no exclusion, so an agent comparing it against show_pattern, show_forms, or show_contrast must infer the boundary itself.

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.