Skip to main content
Glama

Load or initialise the persistent session profile

load_session_profile

Reads the session profile file to provide a unified JSON snapshot of cached artist preferences and past work, resetting to defaults if requested. Ensures agents have context without re-running multiple tools.

Instructions

Reads ~/.tdmcp/session-profile.json (or a custom path) and returns a unified JSON snapshot that an agent should load at the start of every session. The profile caches the most recent outputs of style_memory, recall_similar_work, learn_conventions, and learn_from_my_corpus so the agent has the artist's preferences and past work at hand without running all four tools every time. If no file exists, a default skeleton is created and returned. Pass reset=true to overwrite with fresh defaults. The profile_path field in the returned object is always the resolved path that was read or written.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_pathNoAbsolute path to the session-profile JSON file. Defaults to ~/.tdmcp/session-profile.json.
resetNoIf true, overwrite the existing profile with the built-in defaults and return them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_pathYesAbsolute path of the profile file read or written.
createdYesTrue when the profile was created fresh (no prior file).
resetYesTrue when reset=true was requested.
loaded_atYesISO-8601 timestamp of this read.
style_memoryNoSnapshot from style_memory (Memory/style.md) if previously captured.
recent_workNoTop hits from recall_similar_work if previously captured.
conventionsNoSnapshot from learn_conventions (Memory/conventions.md) if previously captured.
corpus_styleNoSnapshot from learn_from_my_corpus (Memory/corpus_style.md) if previously captured.
notesYesHuman-readable notes about what was loaded or defaulted.
Behavior4/5

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

Annotations show readOnlyHint=false and destructiveHint=false. The description adds behavioral context: it may create a default skeleton if the file is missing and can overwrite with defaults via reset=true. No contradiction with 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?

Three sentences, each contributing: first sentence specifies action and location, second explains caching rationale, third adds edge-case behavior. No redundancy, properly front-loaded.

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?

The description covers purpose, when to use, parameter effects, and edge cases (missing file, reset). With good annotations and output schema, it is sufficient for correct agent invocation.

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 both parameters described. The description restates parameter behavior (default path for profile_path, overwrite for reset) and adds output info about resolved path, but does not significantly enhance schema meaning.

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?

The description clearly states the verb 'reads' and the resource 'session-profile.json', specifying it returns a unified JSON snapshot for agent startup. It also distinguishes from sibling tools like learn_conventions by explaining it caches their outputs.

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

Usage Guidelines4/5

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

The description advises using it at the start of every session and explains its caching benefit over running four other tools. However, it doesn't explicitly state when not to use it or provide alternatives beyond the cached tools.

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/Pantani/tdmcp'

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