Skip to main content
Glama

Save my identity

save_identity

Save or update a standing rule or identity that loads at the start of every future session. Use when the user states something about themselves or how sessions should behave.

Instructions

Saves or updates a standing rule or identity entry that loads at the start of every future session. Use whenever the user states or updates something about themselves or how they want every session to behave: 'my name', 'my role', 'I am', 'I work at', 'my preferences', 'I always', 'from now on', 'always remember', 'my timezone', 'my stack', 'my workflow', 'call me', or any other standing rule or identity anchor. Unlike save_fact (session-scoped context), save_identity is for rules and identity that should govern every future session. Do NOT trigger for one-time facts about a specific task or project (use save_fact instead). Do NOT trigger for information the user explicitly says is temporary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory: identity, preference, client, workflow, technical, standing_rule
keyYesUnique key within category (e.g. 'timezone', 'preferred_stack')
valueYesThe value to store (plain text or JSON string)
priorityNoPriority for loading order (higher = loaded first)
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions persistence across sessions and updates, but does not disclose overwrite behavior, error handling, or permissions. Adequate but missing key behavioral details for a mutation tool.

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?

Description is appropriately sized, front-loads purpose, and each sentence is justified. The usage guidelines are well-structured with explicit examples and exclusions. Slightly verbose but still concise given the necessary detail.

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?

Given no output schema and no annotations, description covers scope, usage boundaries, and distinction from sibling. It implicitly covers update behavior via 'saves or updates'. Leaves some gaps (e.g., what happens if key already exists) but sufficient for typical use.

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%, so baseline 3. Description adds no extra meaning beyond schema; it provides example triggers but does not clarify parameter format or constraints. No value added over schema.

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 verb ('saves or updates'), resource ('standing rule or identity entry'), and scope ('loads at start of every future session'). Distinguishes from sibling save_fact by noting session-scoped vs future session scope.

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?

Explicitly lists when to use (user states/updates identity, preferences, rules) and when not to use (one-time facts, temporary info). Directly names alternative tool save_fact with clear delineation.

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/malamutemayhem/unclick'

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