Skip to main content
Glama

empathetic_reframe

Reframe messages to express genuine empathy by detecting and replacing hollow phrases with authentic alternatives, acknowledging emotions and validating experiences.

Instructions

Reframe a message with genuine empathy — acknowledging emotions, validating experience, and offering presence. Detects and replaces hollow empathy phrases with authentic alternatives. Safety boundary: no manipulation or deceptive empathy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toneNoDesired tone of the empathetic reframewarm
messageYesThe message to reframe with empathy
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: acknowledging emotions, detecting/replacing hollow phrases, and safety constraints. Missing details on return format or processing limits, but overall transparent.

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?

Three focused sentences with no redundancy. Front-loaded with the main action and safety boundary, making it easy to scan.

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?

Given no output schema, the description covers purpose, behavior, and safety adequately. Could be improved by mentioning return type (e.g., reframed message), but still sufficient for correct invocation.

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 coverage is 100%, with clear parameter descriptions. The tool description does not add extra meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 reframes messages with genuine empathy, detects hollow phrases, and sets a safety boundary. It distinguishes from siblings like 'supportive_reply' by focusing on replacing inauthentic empathy.

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 implies use for empathetic reframing and warns against manipulation, but does not explicitly state when not to use or compare to alternatives like 'supportive_reply' or 'deescalation_plan'.

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/humanity4ai/project_human'

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