Skip to main content
Glama

Axad

Structure

show_structure
Read-only

Displays the grammar structure of one sentence, for a learner who wants to see how it is built: each part with its role and word class, and the kind of each clause.

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>",
      "clauses": "<clauses>",
      "lang": "<lang>"
    },
    "name": "show_structure"
  }
}

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
clausesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive, closed-world read, so the safety profile is covered. The description adds that the result is an explanatory breakdown rather than raw data, but it says nothing about the widget/reply framing implied by the fold, next, and note parameters, nor about idempotency despite idempotentHint being false.

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 outcome stated first and the detail list after; no padding. It is dense but every clause carries information about what gets displayed.

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?

With 7 parameters, four required, no output schema, and low schema description coverage, the description should do more: it explains the grammar payload but leaves the sentence/meaning inputs and the widget plumbing (fold, next, note) unexplained. Adequate for understanding the purpose, thin for understanding how to populate the 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?

Schema coverage is 43%, and the two most consequential required parameters, 'say' and 'mean', carry no schema text at all; the description never mentions them, even though the sentence being analyzed presumably comes from 'say'. It does illuminate the 'clauses' structure (kind, parts, role, class), partially compensating for the coverage gap, so a mid score fits.

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 uses a specific verb and resource ('Displays the grammar structure of one sentence') and enumerates the payload exactly ('each part with its role and word class, and the kind of each clause'), which lets an agent picture the output. It does not, however, name or contrast any sibling (show_forms, show_pattern, show_sentence_frame), so the boundary with related display tools must be inferred.

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?

'for a learner who wants to see how it is built' implies an appropriate audience and moment to call it, but there is no explicit when-not clause and no named alternative for adjacent needs such as pattern or forms displays. Usage has to be inferred from the purpose sentence.

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.