Skip to main content
Glama

Check your nervous system state

check_nervous_system_state
Read-onlyIdempotent

Quick nervous system check-in using the three-gear model (wired = fight or flight, safe = rest and digest, flat = shutdown). Classifies the user's current state from how they feel plus energy and tension levels, explains what it means, and returns two or three practices matched to that state with exact steps. Use when someone feels anxious, on edge, numb, burnt out, foggy or asks what state their nervous system is in. Does not store data.

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

Input Schema

NameRequiredDescriptionDefault
how_i_feelNoHow the user feels right now, in their words
energy_levelNoEnergy right now, 1 (empty) to 10 (full)
tension_levelNoTension or stress right now, 1 (calm) to 10 (maxed out)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, and the description adds a consistent non-persistence note ("Does not store data"). It also discloses the internal classification logic and roughly what the response contains (two or three practices with exact steps), though it does not describe the response shape in detail.

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?

The framework definition is front-loaded in a parenthetical, then the classification behavior, then the usage trigger, then the storage disclaimer — a sensible information order. It is somewhat dense in a single paragraph, but no sentence is filler.

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?

With no output schema present, the description must convey return values, and it does: a state classification, an interpretation of what it means, and two or three matched practices with exact steps. Combined with optional parameters and a read-only safety profile, an agent has what it needs to call this correctly; only fine-grained return structure is absent.

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?

Schema description coverage is 100%, so how_i_feel, energy_level, and tension_level are fully documented in the schema, including the 1–10 scale anchors. The description only restates them at a high level ("how they feel plus energy and tension levels") and adds no weighting, defaults, or interaction guidance, so the baseline of 3 applies.

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 names a specific action (a quick nervous-system check-in) and the exact framework used (the three-gear model with wired/safe/flat states), then states the output: a classification plus two or three matched practices with exact steps. That is enough for an agent to tell it apart from siblings like log_daily_check_in or check_pain_flare, which record or assess something else.

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?

It gives concrete triggering conditions — feeling anxious, on edge, numb, burnt out, foggy, or asking what state their nervous system is in — so an agent can route to it without inference. It stops short of naming a sibling to prefer instead, so it is clear-context guidance rather than full when/when-not routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources