Skip to main content
Glama

Record a user preference

mindmap_persona_set

Save standing preferences about your identity, stack, style, communication, constraints, workflow, or goals to persist across sessions. Avoid re-asking by recording user preferences with category and optional project scope.

Instructions

Save a durable preference about how the user works, so future sessions don't re-ask. Use this when the user states a lasting preference — "I prefer X", "always Y", "never Z", "I'm on macOS", "we use Postgres". (For saving a discussion, use mindmap_capture instead — this is for standing preferences.)

Args:

  • text (string): the preference, e.g. "Prefers concise, code-first answers"

  • category: identity | stack | style | communication | constraints | workflow | goals

  • polarity ('prefer'|'avoid'|'fact'): default 'prefer'

  • project (string, optional): scope to one project instead of global Returns: the saved fact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe preference statement
categoryYesWhich dimension this preference is about
polarityNoprefer / avoid / factprefer
projectNoScope to a project (default: global)
Behavior4/5

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

Annotations are present and not contradicted. Description adds durability context ('future sessions don't re-ask') but doesn't specify overwrite or duplicate behavior.

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?

Front-loaded with purpose, then usage guidelines, then argument list. Each sentence is informative and concise.

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?

Despite no output schema, description explains returns. All necessary information for agent invocation is present.

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% with descriptions. The Args section in description mostly mirrors schema, adding minimal extra value.

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?

Description clearly states it saves durable preferences, distinguishes from sibling mindmap_capture, and provides concrete examples of when to use it.

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 usage context: 'when the user states a lasting preference' and alternative tool for saving discussions. Provides clear when-to-use and when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ravi-labs/mindmap-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server