Taste Profile

Save the taste profile

save_profile

DestructiveIdempotent

Use this after the user has confirmed style rules, to keep them as their taste profile. Pass the profile_key and the confirmed layout, palette (#RRGGBB), type, texture and hierarchy rules, things to avoid, and notes; send at least one. It replaces the rules saved before. Returns the saved profile. Do not save rules the user has not agreed to.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Confirmed typography rules.
`avoid`	No	Things the user does not want.
`notes`	No	Anything else the user confirmed. No personal details.
`layout`	No	Confirmed layout rules, each one short and concrete.
`palette`	No	Confirmed colors as #RRGGBB.
`texture`	No	Confirmed texture and finish rules.
`hierarchy`	No	Confirmed visual hierarchy rules.
`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

TableJSON Schema

Name	Required	Description
`as_of`	Yes	UTC date of this answer.
`source`	Yes
`status`	Yes
`profile`	Yes
`retention`	Yes
`saved_day`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

Adds behavior beyond annotations: it replaces previously saved rules (matching destructiveHint=true) and states a return ('Returns the saved profile'). Idempotency is implied by replace semantics. Doesn't detail failure modes or the non-recoverable profile_key consequence, which the schema already carries.

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?

Three tightly packed sentences: precondition first, payload next, destructive replacement and the negative constraint last. No filler; every clause is actionable.

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?

Covers precondition, payload contents, replace semantics, and the confirmation guardrail for an 8-param mutation tool. An output schema exists so return shape need not be explained. Minor gap: no mention of what the destructive replace does to unsaved prior rules beyond 'replaces'.

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 each parameter is already documented, so baseline 3 applies. The description summarizes the same fields (layout, palette, type, texture, hierarchy, avoid, notes) and echoes the '#RRGGBB' format, adding little beyond what the schema states.

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?

States a specific verb+resource ('keep them as their taste profile') and the key precondition (user confirmation). Distinguishes from siblings by describing a save/persist action, though it doesn't explicitly name delete_profile or get_profile as the contrasting operations.

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?

Explicit when-to-use ('after the user has confirmed style rules') and an explicit exclusion ('Do not save rules the user has not agreed to'). This is exactly the precondition and guardrail an agent needs before calling.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.