Skip to main content
Glama

Read how the user works

how_user_works
Read-onlyIdempotent

Retrieves the current ranked profile of how the user thinks, writes, and works so assistants can tailor responses to their habits.

Instructions

Thread's current ranked picture of how the user thinks, writes, and works.

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": "how_user_works"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds that the picture is 'current' and 'ranked,' hinting at a derived, dynamically maintained artifact, but it doesn't say how it is ranked, how fresh it is, or whether it can be empty for a new user.

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?

A single sentence with no filler, which is appropriate for a zero-argument read. It is slightly cryptic in its use of 'Thread's' and 'ranked picture,' but nothing is wasted.

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

Completeness3/5

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

With an output schema present and zero parameters, the description needn't explain return values or arguments. What remains missing is routing guidance against the other memory/learning tools, which is the main thing an agent needs to invoke this correctly.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading parameter language is present.

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 identifies a specific resource — a synthesized, ranked profile of how the user thinks, writes, and works — which is meaningfully different from raw memory or voice notes. The verb 'Read' appears only in the title, not the description, and no sibling is named, so differentiation is inferable rather than explicit.

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?

There is no when-to-use guidance at all, despite a crowded sibling set (learn_about_user, note_user_voice, list_memory, search_memory, read_chat) where the choice matters. The agent must guess whether this is the preferred source for personalization versus querying individual memories.

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