Skip to main content
Glama

Get a plan for a hard moment

get_moment_guide
Read-onlyIdempotent

Gives a short, step-by-step, body-first plan for one specific hard moment, from Recalibrate's Calming the Nervous System guides: 3 a.m. wake-up, panic attack, Sunday dread, nerves before a meeting or presentation, afternoon energy crash, after an argument, anger, or overthinking. Each plan has 3 to 4 evidence-informed techniques with exact steps and a safety note. Pass a moment, or describe the situation and the best match is chosen. 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": "get_moment_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
momentNoThe moment, if known
situationNoWhat the user is going through, in their words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds that each plan contains 3-4 evidence-informed techniques with exact steps plus a safety note, and that nothing is stored. It does not say what happens if neither parameter is passed, which is a meaningful gap for a zero-required-param tool.

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 purpose and the call pattern are front-loaded, and the middle enumeration of moments maps directly to the enum values. It is slightly long but nearly every clause carries information an agent can act on.

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?

With no output schema, the description supplies the return shape (3-4 techniques with steps and a safety note) and a data-handling statement. For a two-parameter, read-only lookup tool nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining the relationship between the two parameters - a known moment versus a free-text situation where 'the best match is chosen' - and by listing moment values that mirror the enum.

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?

States a concrete verb and resource: 'Gives a short, step-by-step, body-first plan for one specific hard moment', and enumerates the eight supported moments. It does not differentiate itself from the sibling start_calm_exercise or the lesson tools, so an agent must infer the boundary.

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?

It explains how to call it ('Pass a moment, or describe the situation and the best match is chosen'), which is real usage guidance, and the target situation is clearly implied. But it gives no when-not guidance and no routing against siblings such as start_calm_exercise.

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