Skip to main content
Glama
worakorn-prince

th-memory-mcp

by worakorn-prince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get user profile

get_profile

Get the distilled user profile: profile sections, top preferences by confidence (max 15), and the 5 most recent lessons. Optional userId/sessionId/projectId scope the auto-projected memories; without them only GLOBAL memories are included.

Instructions

Get the distilled user profile: profile sections, top preferences by confidence (max 15), and the 5 most recent lessons. Optional userId/sessionId/projectId scope the auto-projected memories; without them only GLOBAL memories are included.

Input Schema

NameRequiredDescriptionDefault
userIdNoInclude GLOBAL plus this user's USER-scoped memories
projectIdNoInclude GLOBAL plus this project's PROJECT-scoped memories
sessionIdNoInclude GLOBAL plus this session's SESSION-scoped memories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.3.5
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Include GLOBAL plus this project's PROJECT-scoped memories",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Include GLOBAL plus this session's SESSION-scoped memories",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / userId
      Added value: +{
+  "description": "Include GLOBAL plus this user's USER-scoped memories",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observedv2.2.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the exact shape of the response (sections, capped preference list of 15, 5 lessons) and the default GLOBAL-only scoping behavior. It omits any statement about permissions, cost, or whether the call is purely read-only, but 'Get' plus the content list makes the operation's nature clear.

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 dense sentences with no waste: the first front-loads what is returned, the second front-loads the scoping rule. Nothing is repeated from the schema verbatim.

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?

With no annotations and no output schema, the description must supply both behavior and return shape, and it does: return contents are enumerated and the default scope is stated. Only minor gaps remain (read-only confirmation, auth or timing expectations) for a tool this simple with three optional params.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns one extra by explaining the collective effect of the params ('scope the auto-projected memories') and the no-param default (GLOBAL only), which the per-field schema descriptions only imply individually.

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 and resource ('Get the distilled user profile') and enumerates the returned contents: profile sections, top preferences by confidence (max 15), and the 5 most recent lessons. This clearly separates it from data-heavy siblings like recall or search_history, though it never names those siblings directly.

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

Usage Guidelines3/5

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

The second sentence gives a real usage rule: 'without [scope params] only GLOBAL memories are included,' which tells the agent how scoping changes results. However, there is no explicit guidance on when to choose get_profile over recall, get_context, or search_history, so the agent must infer the alternative.

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

Deploy Server

Other Tools