Skip to main content
Glama

ingest

Send biometric signals from any sensor—heart rate, vocal tone, facial expression, or text sentiment—to receive a unified psychological state with stress scoring and cross-session topic tracking.

Instructions

Send biometric signals from any sensor, get unified state back.

Required: session_id + timestamp (ISO 8601) + at least one signal.
Send whatever you have — the API fuses all signals into one state.

Common signals (highest impact):
- heart_rate (bpm, 30-220) + rmssd (ms) — cardiovascular
- tone: calm | tense | anxious | hostile — vocal
- sentiment: -1.0 to 1.0 — textual
- expression: relaxed | neutral | tense — visual

For trigger memory (cross-session psychological tracking):
- Include subject_id (consistent per user, hashed)
- Include user_message + ai_response to detect stress topics

Returns same fields as get_human_state plus signals_received list and topics_detected.

source_device is optional but improves confidence scoring. Not a medical device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
timestampYes
heart_rateNo
rmssdNo
sdnnNo
spo2No
pnn50No
mean_ibiNo
ibi_countNo
toneNo
speech_rateNo
pitch_variabilityNo
expressionNo
gazeNo
postureNo
engagementNo
sentimentNo
urgencyNo
glucose_mg_dlNo
glucose_mmol_lNo
glucose_trendNo
eeg_alpha_powerNo
eeg_beta_powerNo
eeg_theta_powerNo
cognitive_loadNo
edaNo
skin_temperatureNo
respiratory_rateNo
steps_last_minuteNo
activity_levelNo
sleep_stageNo
stress_scoreNo
source_deviceNo
confidenceNo
subject_idNo
user_messageNo
ai_responseNo
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses fusion behavior ('API fuses all signals into one state'), return value composition (mirrors get_human_state plus extras), confidence scoring dependency on source_device, and critical safety disclaimer ('Not a medical device'). Minor gap on rate limits or error handling.

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?

Excellently structured with clear hierarchy: core purpose → requirements → signal taxonomy (bullet points with units/enums) → trigger memory context → return values → safety note. No wasted sentences; front-loaded with essential action statement.

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 complex 37-parameter biometric tool with no output schema, description adequately explains return structure by referencing sibling tool fields plus additions. Covers required vs optional fields, units, enums, and safety scope. Would need error handling or rate limit notes for a 5.

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

Parameters5/5

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

Schema has 0% description coverage (titles only). Description richly compensates by documenting: timestamp format (ISO 8601), heart_rate units/range (bpm, 30-220), tone enum values (calm|tense|anxious|hostile), sentiment range (-1.0 to 1.0), subject_id hashing requirement, and source_device impact on confidence scoring.

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?

Opens with specific verb-resource pair ('Send biometric signals... get unified state'). Distinguishes from sibling get_human_state by noting it 'Returns same fields as get_human_state plus signals_received list and topics_detected', clarifying this is the write/ingest path versus the read path.

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?

Provides clear contextual guidance on when to include optional parameters ('For trigger memory... Include subject_id... user_message + ai_response'). Implicitly contrasts with get_human_state via return value description, though lacks explicit 'when not to use' exclusions.

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