Skip to main content
Glama

Get user profile

get_profile

Retrieve a distilled user profile with top preferences and recent lessons, optionally scoped by user, project, or session to tailor AI responses.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profile"
  }
}

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. Changed1 schema field changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. 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"
      +  ]
      +}
  3. First observedv2.2.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and it does disclose the non-obvious behavioral detail that omitting all scope parameters silently restricts results to GLOBAL memories, plus hard caps on preference and lesson counts. It does not describe authorization, error behavior, or whether the read is cheap or expensive, but the important surprise is surfaced.

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?

Two sentences with no filler, contents listed first and scoping second, which is the right order for an agent. Slightly dense jargon ("distilled", "auto-projected") costs a little readability.

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?

For a zero-required-parameter read tool with no output schema and full schema coverage, the description gives enough: what comes back, how much of it, and how scoping reshapes the result. Only the absence of any return-shape detail (structure versus plain text) keeps it from being fully complete.

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, and the description earns an extra point by explaining how the three scope parameters interact with the auto-projected memory set and what happens when none are supplied. The per-parameter "GLOBAL plus X" wording is largely duplicative of the schema, but the omission default is added value.

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?

"Get the distilled user profile" pairs a specific verb with a resource, and the description enumerates the returned contents (profile sections, top preferences by confidence capped at 15, 5 most recent lessons). It is clear on its own but never names a sibling such as get_context or recall, so an agent must infer the boundary from names alone.

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?

It states the default behavior when no scope is given (GLOBAL memories only), which is effectively a when-not condition and steers parameter choice. However, it offers no guidance on when to choose this over recall, get_context, or search_history, leaving the sibling routing to inference.

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