Taste Profile

Search reference images

search_refs

Read-onlyIdempotent

Use this when the user wants to find references they saved, by words such as "dark editorial layout with a serif headline", or by giving another image to find similar ones. Pass the profile_key and exactly one of query_text, query_image_url or query_file. Returns the closest references with their name, summary, palette and a closeness score. It searches only this user's saved references, never the web.

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": {
      "query_text": "dark editorial layout with a serif headline",
      "profile_key": "tp_604a48a85c9a4da5a2a15ba7b4198f1b"
    },
    "name": "search_refs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many matches to return; default 5.
`query_file`	No	An uploaded image to find similar references for.
`query_text`	No	Words describing the look to find, such as "dark editorial layout with a serif headline".
`profile_key`	Yes	The profile_key that add_refs returned. Keep it: it is the only way back to this profile and it is not recoverable.
`query_image_url`	No	A public https link to an image to find similar references for.

Output Schema

Name	Required	Description
`as_of`	Yes	UTC date of this answer.
`query`	Yes
`notice`	Yes
`source`	Yes
`status`	Yes
`matches`	Yes
`refs_total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "profile_key": "tp_604a48a85c9a4da5a2a15ba7b4198f1b",
+    "query_text": "dark editorial layout with a serif headline"
+  }
+]

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

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description instead contributes the corpus boundary ('never the web'), the one-of input constraint, and the result shape including a closeness score. Those are genuine additions beyond the structured fields. Minor tension worth noting: openWorldHint=true while the description insists the search is confined to saved references, though this reads as scoping rather than a real conflict.

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 the trigger condition, then inputs, then outputs, then scope — a sensible order with no filler sentences. The return-value list mildly duplicates the existing output schema, costing a little density.

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?

With full schema coverage, an output schema, and complete annotations, the description only needed to supply trigger, input-exclusivity and corpus scope — and it supplies all three. An agent can select and invoke this correctly without further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds a constraint the schema does not encode: exactly one of query_text, query_image_url or query_file. That single sentence prevents a class of malformed calls the schema alone would permit.

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 ('find references they saved') and immediately bounds the corpus ('only this user's saved references, never the web'), which separates it from any web-search or style-description sibling. The two query modes (text or image) are named up front, so an agent knows the shape of the operation before opening the schema.

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 find references they saved' gives a clear trigger, and the mutual-exclusivity rule ('exactly one of query_text, query_image_url or query_file') is an explicit usage constraint. It stops short of naming an alternative sibling (e.g. describe_style) or stating when not to use it, so it is clear context rather than full routing guidance.

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.