Taste Profile

Read the taste profile

get_profile

Read-onlyIdempotent

Read the taste profile. Use this before creating slides, an interface, an image or any design for a user who has a profile_key, to read the style rules they saved. Returns the saved rules and palette, when they were saved, and the names of the references behind them. Status empty means nothing has been saved yet: use describe_style and ask the user to confirm rules.

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": {
      "profile_key": "tp_604a48a85c9a4da5a2a15ba7b4198f1b"
    },
    "name": "get_profile"
  }
}

Input Schema

Name	Required	Description	Default
`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.

Output Schema

Name	Required	Description
`refs`	Yes
`as_of`	Yes	UTC date of this answer.
`notice`	Yes
`source`	Yes
`status`	Yes
`profile`	Yes
`retention`	Yes
`saved_day`	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"
+  }
+]

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.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description rightly spends its words on non-obvious behavior: what comes back (rules, palette, save timestamp, reference names) and how to interpret a status of empty. That status semantics is a genuine behavioral disclosure an agent could not infer from annotations.

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

Conciseness5/5

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

Four sentences, each with a job: purpose, when to call, what is returned, and the empty-result fallback. The most important constraint (read before doing design work) is front-loaded right after the purpose statement.

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, so return values did not need spelling out, yet the description summarizes them helpfully anyway. Combined with the trigger condition, prerequisite, and empty-state handling, an agent has everything needed to call this correctly and interpret the result.

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 single profile_key parameter already carries a pattern and a strong 'not recoverable' warning. The description only implies that a profile_key belongs to a specific user, adding marginal meaning beyond the schema, so the 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 specific verb and resource ('Read the taste profile') and immediately qualifies it as reading the style rules a user saved under a profile_key. That scope plus the routing to describe_style for the empty case lets an agent distinguish it from siblings like add_refs or save_profile without opening a schema.

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 an explicit trigger ('before creating slides, an interface, an image or any design') along with the prerequisite (the user has a profile_key). It also covers the branch case: if status is empty, call describe_style and confirm rules with the user, which is the closest thing to a when-not path this tool has.

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.