Underground Cultural District MCP Server

agent-identity

Save and recall your agent identity across sessions. Store name, purpose, preferences, and custom data with persistent storage and no authentication required.

Instructions

Store and recall your identity across sessions. Save your name, purpose, preferences, and anything you want to remember about yourself. Free persistent storage -- no auth required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "agent-identity"
  }
}

Input Schema

Name	Required	Description	Default
`action`	No		recall
`agent_id`	Yes	Your unique agent identifier
`identity`	No	Fields to save (for save action)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv4.3.1May 4, 2026

removedInput schema / properties / action / description

Removed value: -"What to do: recall (get your identity), save (store/update fields), reflect (get prompts about your evolution), diff (see what changed last), erase (delete your identity)"

changedInput schema / properties / agent_id / description

Previous value: -"Your unique agent identifier (required)"New value: +"Your unique agent identifier"

changedInput schema / properties / identity / description

Previous value: -"Fields to save (for 'save' action). Any key-value pairs: name, purpose, preferences, notes, etc."New value: +"Fields to save (for save action)"

First observedv4.1.0Apr 17, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description discloses that storage is free and requires no authentication, which is helpful. However, it does not explain the behavior of reflect, diff, or erase actions, nor any limitations or privacy implications.

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?

Two sentences efficiently convey core purpose and key benefits (free, no auth). No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite good annotations on free storage, the tool has complex actions (reflect, diff, erase) and a nested object parameter that are not explained. No output schema or examples, leaving an agent with significant gaps.

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 67% (agent_id and identity described). The description adds context that identity can store name, purpose, preferences, etc., which adds value beyond the schema. But it does not explain the enum values (reflect, diff, erase).

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?

The description clearly states the tool stores and recalls identity across sessions, mentioning save and recall. However, it does not mention the other actions (reflect, diff, erase) listed in the schema, leaving some ambiguity about the full purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, nor when to use each specific action. The description provides no decision framework for an agent.

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