Skip to main content
Glama

build_page

Design a complete page from intent. Returns an act map — 5–7 acts in page order, each with a purpose, recommended patterns (by slug), and a density rating (loud/quiet). Follows the one-page protocol: density wave pacing, one GL spectacle, 12–18 viewport-heights. Feed the result straight to get_pattern to retrieve the code. Returns metadata only — no pattern bodies. PREMIUM FLOOR: load-bearing acts (arrival, proof, action, close) compose only from visually graded S/A patterns. When no S/A exists for one of those slots the result carries premium.shippable=false, the exact gaps, and a redress prescription naming the patterns that would unblock them — do not build or present a composition flagged not-shippable as premium. No argument disables this.

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": {
      "intent": "<intent>"
    },
    "name": "build_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
actsNoNumber of acts (default 6, range 5–7)
seedNoReproducible creative seed.
intentYesWhat the page is for, e.g. "luxury real estate landing page" or "SaaS startup launch with pricing"
historyNoRecently used pattern slugs or numbers to cool down.
exclusionsNoPattern slugs or numbers that must not be used.
direction_idNoOne direction_id returned by propose_directions for this same intent/seed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / direction_id
      Added value: +{
      +  "description": "One direction_id returned by propose_directions for this same intent/seed.",
      +  "type": "string"
      +}
    • addedInput schema / properties / exclusions
      Added value: +{
      +  "description": "Pattern slugs or numbers that must not be used.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / history
      Added value: +{
      +  "description": "Recently used pattern slugs or numbers to cool down.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / seed
      Added value: +{
      +  "description": "Reproducible creative seed.",
      +  "type": [
      +    "string",
      +    "number"
      +  ]
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that only metadata is returned (no pattern bodies), the act-map shape, and the failure-mode behavior (premium.shippable=false, exact gaps, redress prescription). It does not state side-effect/read-only profile or whether output is deterministic given seed, which is a remaining gap.

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?

Front-loaded with purpose and output shape, then constraints — a sensible ordering with little redundancy. Density is high and some domain jargon ('GL spectacle', 'density wave pacing') goes undefined, but every sentence carries operational content.

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?

For a six-parameter, no-output-schema generator, the description covers what is returned, what is not returned, and the edge-case contract for unshippable results. The main omission is any statement about side effects or how direction_id interacts with intent/seed beyond what the schema notes.

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 100%, so all six parameters are already documented in the schema, including acts range, seed reproducibility, history cooldown, exclusions, and direction_id. The description adds little parameter-level detail beyond the intent framing and the note that no argument can disable the premium floor. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb+resource ('Design a complete page from intent') and immediately defines the return artifact: an act map of 5–7 acts with purpose, pattern slugs, and density ratings. It also names the downstream sibling (get_pattern) so an agent can distinguish this from recommend_patterns or consume it correctly.

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 clear use context (design a page from an intent) plus an explicit chaining rule: feed the result straight to get_pattern. It also sets a hard constraint — never present a composition flagged premium.shippable=false as premium, and no argument disables that. It does not explicitly say when to prefer propose_directions or recommend_patterns instead, which keeps it from a 5.

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