Skip to main content
Glama

Get layout

get_layout
Read-onlyIdempotent

Return one layout as a ready-to-use, self-contained document: HTML, theme CSS, and its slot definitions. Call this once the user knows which layout they want, or with ids returned by suggest_deck.

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": {
      "id": "<id>"
    },
    "name": "get_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLayout id from list_layouts or suggest_deck.
langNoLanguage for slot hints and usage notes. Pass the language the user is writing in.ko
theme_idNoTheme id or custom:<uuid>. Omit to use the layout's default theme.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Layout id from list_layouts or suggest_deck."
    • addedInput schema / properties / theme_id / description
      Added value: +"Theme id or custom:<uuid>. Omit to use the layout's default theme."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description does add real value by disclosing the shape of the response — a self-contained document bundling HTML, theme CSS, and slot definitions — which matters because there is no output schema. It says nothing about payload size, caching, or failure behavior for an invalid id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The return payload is front-loaded and the invocation condition follows, so an agent can act after the first read.

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

Completeness4/5

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

With no output schema, the description correctly compensates by summarizing the returned document and its parts, and the three parameters are fully covered by the schema. What remains unaddressed — error behavior for unknown ids, and whether theme_id overrides the bundled CSS — is minor for a read-only fetch.

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 description coverage is 100%, so id, lang, and theme_id are already fully documented, including the enum and the custom:<uuid> form. The description only reinforces where ids come from (suggest_deck), adding no syntax or behavior beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 ("Return one layout") and enumerates the payload (HTML, theme CSS, slot definitions), which distinguishes it from list_layouts by making clear it fetches a single fully-resolved layout rather than a collection. It stops short of naming the sibling it replaces, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions: call once the user has settled on a layout, or with ids returned by suggest_deck. That routes the agent well against suggest_deck and list_layouts. It does not state any when-not condition (e.g., don't call to browse options), so it is clear context without exclusions.

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.

Resources