Skip to main content
Glama

Describe a Seedwall look

describe_look
Read-onlyIdempotent

Retrieve a generative look's colours, shapes, density, text layer and preset options so you can pick the correct parameter values before rendering SVG or PNG artwork.

Instructions

Shows one look's parameters (colours, shapes, density, text layer) and its presets, so you can set params when rendering.

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": {
      "look": "<look>"
    },
    "name": "describe_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookYesLook id from list_looks, e.g. topographic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description usefully discloses what the response contains (parameters and presets), which matters because there is no output schema, but says nothing about behavior for an unknown or invalid look id.

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 compact, front-loaded sentence with no filler. The parenthetical field list earns its place by previewing the payload.

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 single-parameter read tool with no output schema, the description covers purpose, payload shape and the downstream use (configuring render). Error handling for bad ids is the only notable omission.

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% and the schema already tells the agent the value is a look id from list_looks with the example 'topographic'. The description adds no format or validation detail beyond that, so the baseline 3 applies.

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 concrete verb and resource: retrieves one look's parameters (colours, shapes, density, text layer) plus its presets. This clearly separates it from list_looks, which enumerates looks, though it never names that sibling outright.

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 clause 'so you can set params when rendering' implies when to call it, namely before render, but gives no explicit when-not and does not point at list_looks for discovering ids.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools