Skip to main content
Glama

get_trigger_memory

Retrieve a subject's psychological trigger profile, revealing which conversation topics consistently cause stress (active triggers) and which have resolved over time, based on prior stress data.

Instructions

Retrieve psychological trigger profile for a subject.

Returns which conversation topics consistently cause stress (active triggers) and which have been resolved over time.

- active triggers: topics where stress was elevated across multiple sessions. Tread carefully.
- resolved triggers: topics where stress has decreased. Safe to explore deeper.

Each trigger includes observation_count, avg_score, peak_score, and last_seen.

Requires prior ingest calls with the same subject_id. Not a medical device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subject_idYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It declares the tool is read-only by nature, describes the returned data structure (active vs resolved triggers with field details), and includes a disclaimer ('Not a medical device'). This is thorough, though it does not explicitly state side effects (none expected).

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?

The description is concise and well-structured: a clear first sentence, then bullet points explaining trigger types and fields. Every sentence adds value, with no unnecessary repetition or fluff.

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?

For a tool with one parameter and no output schema, the description covers purpose, return values (including fields), prerequisites, and a disclaimer. It is sufficient for an AI agent to understand and use the tool correctly.

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?

The schema has only 'subject_id' with 0% description coverage. The description implies the parameter identifies the subject via the prerequisite statement, but provides no additional details on format, source, or constraints. This adds some context beyond the schema, but not enough to fully compensate for the lack of schema documentation.

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 tool retrieves a 'psychological trigger profile' and explains it returns active and resolved triggers. It differentiates from siblings like ingest and get_human_state by focusing on trigger memory.

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 description mentions a prerequisite ('requires prior ingest calls') but does not provide explicit guidance on when to use this tool versus alternatives. No exclusions or relative advantages are stated.

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/nefesh-ai/nefesh-mcp-server'

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