Taste Profile

Add reference images

add_refs

Use this when the user wants to keep images as design references: uploaded images or public links to image files, up to 4 per call. Each image is read once and kept as a style description with its layout, color palette (hex), typography, texture and hierarchy; the image itself is not stored. Leave out profile_key to start a new profile, or pass the key from an earlier call to add to it. Returns the profile_key (keep it), what was added and any image that could not be read. It does not open web pages, search for images or identify people.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": [
        "https://images.example.com/poster.png"
      ]
    },
    "name": "add_refs"
  }
}

Input Schema

Name	Required	Description
`urls`	No	Public https links that open one image directly (PNG, JPEG, GIF or WebP), at most 4 per call, files and links together. Pages that show an image do not work.
`files`	No	Images the user uploaded, at most 4 per call (PNG, JPEG, GIF or WebP).
`profile_key`	No	Leave out to start a new profile; pass the key from an earlier add_refs to add to that profile.

Output Schema

Name	Required	Description
`added`	Yes
`as_of`	Yes	UTC date of this answer.
`failed`	Yes
`notice`	Yes
`source`	Yes
`status`	Yes
`refs_max`	Yes
`retention`	Yes
`refs_total`	Yes
`profile_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "urls": [
+      "https://images.example.com/poster.png"
+    ]
+  }
+]

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only flag non-read-only, open-world, non-idempotent and non-destructive; the description adds the facts that matter: each image is read once, the image itself is not stored (only a derived description), partial failures are reported, and the returned profile_key must be kept. This is meaningful behavior beyond the structured hints.

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?

It is front-loaded with the usage trigger and packs the important constraints (limit of 4, image not stored, profile_key handling) into a short block. The middle sentence is dense with clauses, but nothing is redundant filler.

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?

An output schema exists, and the description still briefly previews the return (profile_key, what was added, unreadable images), plus input-type limits and exclusions. For a 3-parameter tool with no required fields, this covers everything an agent needs to call it correctly.

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 both urls and profile_key semantics are already in the schema. The description restates the 4-per-call limit and profile_key lifecycle, adding continuity context (start a new profile vs. append using a key from an earlier call) but no format or syntax detail beyond the schema; baseline 3 applies.

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 concrete verb and resource ('keep images as design references', 'uploaded images or public links') and explains the transformation: images become a style description with layout, palette, typography, texture and hierarchy. That distinguishes it clearly from siblings like describe_style or search_refs, which the agent can rule out without opening their schemas.

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?

'Use this when the user wants to keep images as design references' gives an explicit trigger, and the profile_key sentence explains the two usage modes (new vs. append). The negative boundaries ('does not open web pages, search for images or identify people') help exclusion, though no sibling tool is named as the alternative for those cases.

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

All Taste Profile tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.