Skip to main content
Glama

get_taste_interview

Read-onlyIdempotent

Calibrates a new project's design taste by returning a short structured interview, or re-interviews an already-bound project after rejected output to pinpoint and fix what fell short.

Instructions

START HERE on a NEW project: returns a deterministic calibration interview. By default (depth:'first_run') it is COMPRESSED to just 6 core questions — identity, customer (who it is for, what they are trying to do when they arrive, what would make them leave; stored as design_notes.customer), genesis (what already exists for the project — a brand, a design system, brand assets — routing whatever is missing to generation: mood board approval stop, then generate_design_system save:true, then init_design_md), aesthetic, voice, matchers — so a first-time kickoff is fast; every other question (references, the remaining ten design dimensions, any learned dimensions, rule exceptions, and the open-ended special question) is still returned under more_questions for the agent to offer as optional deeper calibration. Pass depth:'full' to get everything at once as a single flat questions list (the eleven design dimensions — typography, spacing, color, layout, motion, imagery, entrance, loading, navigation, aesthetic, libraries — each grounded in what the profile already enforces and most carrying multiple-choice options; the libraries question names specialty tech in plain outcome language and states the default build target for sites: a Next.js app, unless the user prefers otherwise). The voice question always renders the same message in three registers (formal-technical / warm-conversational / punchy-editorial) so the user picks by ear, not by adjective — asked even when the profile has zero voice rules. Every question carries skippable + priority ('core'|'extended'); only identity is required. A 'references' question (offered in more_questions on first_run) invites example URLs/screenshots/files, each interviewed with follow-ups about what specifically draws the person, folded into the matching design_notes. The full interview closes with an open-ended 'special' question (any texture, signature detail, motif, or easter egg nothing else asked about); once the person has other bound surfaces, it carries suggestions — the special touches they chose elsewhere. Ask the user the returned questions conversationally, then persist the answers with bind_taste_surface (dimension answers go in design_notes). Run this BEFORE the first audit_taste on any project that has no binding yet — audit results include a calibration_hint when calibration is missing. When a user dislikes generated/designed output on an ALREADY-calibrated project, re-run with mode:'refine' instead of starting over — dissatisfaction is a calibration signal, not a dead end: it requires an existing binding, then interviews what specifically fell short, offers to keep/tighten/replace each stored design_notes value, re-asks voice, and offers to log a reject precedent via label_finding. mode defaults to 'kickoff'.

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": {
      "profile": "<profile>"
    },
    "name": "get_taste_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'kickoff' (default) calibrates a project with no binding yet. 'refine' re-interviews an ALREADY-bound project after the user rejects generated/designed output — requires an existing binding (throws naming get_taste_interview kickoff otherwise) and asks what fell short, then per-dimension keep/tighten/replace, then voice, then an optional reject precedent.
depthNo'first_run' (default) returns only the 6 core questions (identity, customer, genesis, aesthetic, voice, matchers) plus a `more_questions` array with everything else for optional deeper calibration. 'full' returns every question flattened into `questions`, as before.
profileYesTaste profile name (see list_taste_profiles).
projectNoProject identifier the binding will be saved under, e.g. 'raven-mcp' or 'portfolio'. Include it so the interview can show any existing binding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / depth / description
      Previous value: -"'first_run' (default) returns only the 5 core questions (identity, genesis, aesthetic, voice, matchers) plus a `more_questions` array with everything else for optional deeper calibration. 'full' returns every question flattened into `questions`, as before."New value: +"'first_run' (default) returns only the 6 core questions (identity, customer, genesis, aesthetic, voice, matchers) plus a `more_questions` array with everything else for optional deeper calibration. 'full' returns every question flattened into `questions`, as before."
  2. Changed1 schema field changedv2.5.1
    • changedInput schema / properties / depth / description
      Previous value: -"'first_run' (default) returns only the 4 core questions (identity, aesthetic, voice, matchers) plus a `more_questions` array with everything else for optional deeper calibration. 'full' returns every question flattened into `questions`, as before."New value: +"'first_run' (default) returns only the 5 core questions (identity, genesis, aesthetic, voice, matchers) plus a `more_questions` array with everything else for optional deeper calibration. 'full' returns every question flattened into `questions`, as before."
  3. First observedv2.2.9

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses default depth behaviour, what lands in `more_questions` versus `questions`, that only the identity question is required, and that refine throws if no binding exists. That is exactly the operational context an agent needs before calling.

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

Conciseness3/5

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

The lead ('START HERE on a NEW project') is well front-loaded, but the body is a dense wall of run-on sentences and parentheticals listing every question type. Much of that inventory is useful, yet it could be trimmed substantially without losing selection-relevant information.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing the return value, and it does: question list shape, skippable/priority flags, the three-register voice question, the references follow-ups, and the closing special question with suggestions. Nothing an agent needs in order to call and use the result is missing.

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% and the schema's own mode/depth descriptions already cover the defaults and the refine precondition, so the description largely restates structured data. It adds some framing around profile and project ('include it so the interview can show any existing binding'), but no syntax or format detail the schema lacks.

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?

States a specific verb and resource: 'returns a deterministic calibration interview' for a taste profile, and immediately marks it as the entry point ('START HERE on a NEW project'). It is clearly distinguishable from siblings like audit_taste (which consumes calibration) and bind_taste_surface (which persists answers).

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

Usage Guidelines5/5

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

Gives explicit when-to-use rules: run before the first audit_taste on any project with no binding, and re-run with mode:'refine' when a user rejects output on an already-calibrated project. It names the alternative behaviour ('instead of starting over') and the fallback signal (calibration_hint in audit results).

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