Skip to main content
Glama

Propose visual style directions

inspo_add_styles

Adds 3-6 visual style directions to a board, fetching CC-licensed photos and rendering your product in each style as votable live specimens.

Instructions

Add 3-6 visual STYLE directions to the board. For each one inspo fetches real CC-licensed photos (Openverse), and renders the user's own product in that style — a landing page for websites, a dashboard for web systems, three phone screens for mobile apps — (palette, fonts, layout, image treatment, texture) as a live specimen they can vote on. Start from presets and override palette/fonts to fit the brand, or pass custom html.

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": {
      "styles": "<styles>"
    },
    "name": "inspo_add_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
copyNoOverride the session copy for these specimens.
stylesYes
sessionNoSession id. Defaults to the most recent session in this project.
imageSubjectNoWhat the photos should show, in English, e.g. "coffee beans roastery". Combined with each style's imageQuery.
imagesPerStyleNoDefault 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/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 disclose meaningful behavior: it appends to the board, makes external Openverse calls for CC-licensed photos, and renders live specimens the user can vote on. It also explains the surface default mapping. It does not cover failure modes, latency/cost of image fetching, or what happens to previously added styles.

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?

Two sentences with the core action front-loaded, followed by the mechanism and the input options. The long parenthetical lists are dense but they carry real information; the only wasted motion is a mild redundancy between the enumerated style qualities and the schema fields.

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 nested-object mutation tool with 80% schema coverage and no output schema, the definition covers purpose, rendering behavior, external image sourcing, and input strategy. The remaining gaps are the 3-6 vs. maxItems 16 count mismatch and no statement of what the tool returns or how votes/board state look afterward.

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 80%, so the schema already explains most parameters, making 3 the baseline. The description adds light context by naming the preset-then-override pattern and the custom html escape hatch, but it does not clarify the 'styles' array item fields beyond what the schema states, and it says '3-6' styles while the schema permits 1-16.

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 gives a specific verb and resource ('Add 3-6 visual STYLE directions to the board') and elaborates on what a direction consists of (palette, fonts, layout, image treatment, texture) and how it is rendered (landing page, dashboard, phone screens). It is clear what the tool produces, but it never explicitly distinguishes itself from near-siblings like inspo_add_component, inspo_add_images, or inspo_add_build.

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?

'Start from presets and override palette/fonts to fit the brand, or pass custom html' tells the agent how to shape the input, and the voting/specimen framing implies the use case (proposing directions for user review). However, there is no explicit when-to-use versus when-not, no mention of prerequisites such as an active session, and no routing to sibling tools for adjacent tasks.

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