Skip to main content
Glama

Nefesh — Real-Time Human State Awareness for AI

by ai.nefesh

request_api_key

Request a free Nefesh API key. No existing API key needed for this call.

IMPORTANT: You MUST ask the user for their real email address before
calling this tool. Do NOT invent, guess, or generate an email address.
The user will receive a verification link they must click to activate
the key. Without clicking that link, no API key will be issued.
Disposable or temporary email services are blocked.

Example prompt to the user: "What is your email address? You will
receive a verification link to activate your free API key."

Flow: call this with the user's real email, then poll
check_api_key_status every 10 seconds until status is 'ready'.

Free tier: 1,000 calls/month, all signal types, 10 req/min. No credit card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses critical behaviors: the verification link must be clicked, disposable email services are blocked, the polling flow, and free tier limits. This exceeds what annotations would typically provide, giving the agent complete awareness of side effects and prerequisites.

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 appropriately structured: a clear opening statement, an IMPORTANT note with a user prompt example, a flow instruction, and free tier details. Every sentence adds value, and the text is front-loaded with purpose. Despite its length, there is no redundant or filler content.

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?

The description covers the overall flow, prerequisites, and behavioral constraints well. However, it does not explicitly state what request_api_key returns (e.g., a request ID or confirmation), which would be needed to fully understand the polling step. Minor gap, but the flow is otherwise complete.

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?

The schema only defines 'email' as a string with zero description coverage. The description compensates by explaining that the email must be the user's real email, cannot be invented or disposable, and is used for the verification link. This adds essential meaning beyond the schema.

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 opens with a specific verb+resource: 'Request a free Nefesh API key.' It clearly distinguishes this tool from its siblings, especially check_api_key_status, by describing the polling flow that follows. 'No existing API key needed for this call' further clarifies the tool's role.

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

Usage Guidelines5/5

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

The description provides explicit when and how to use the tool: ask the user for their real email first, do not invent one, and then poll check_api_key_status. It also gives an alternative for checking status, along with rate limits and free tier constraints, making usage guidance thorough.

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

All Nefesh — Real-Time Human State Awareness for AI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: API key request/status, data ingestion, current state retrieval, session history, and trigger memory. No two tools overlap in functionality or could be confused.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., request_api_key, get_human_state, get_session_history). This creates a predictable and intuitive naming convention across the entire set.

Tool Count5/5

Six tools is well-scoped for a real-time human state awareness API, covering the essential lifecycle (key management, data intake, state access, history, and psychological insights) without redundancy or bloat.

Completeness5/5

The tool surface fully covers the core domain: authentication (request and check key), data ingestion, current state, historical trends, and cross-session trigger profiles. There are no obvious missing operations for the stated purpose.

Resources