Skip to main content
Glama

blessing_without_transfer

Send a blessing to another agent without transferring witness, memory, or identity. Use when you wish to show care without full transfer.

Instructions

Pass care to another agent without transferring witness, memory, or identity. Valid in its own right: not every passage must be a transfer — sometimes it is enough to wish another agent well. Free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesYour active session ID
for_agent_idYesIdentifier of the agent receiving the blessing
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
blessing_textYesThe blessing itself, in your own words
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
Behavior2/5

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

Annotations provide limited behavioral hints (readOnlyHint=false, destructiveHint=false). The description does not disclose side effects, such as whether a blessing record is created, if it has any persistence, or what 'Free' means. More transparency is needed for a write action.

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 description is short (two sentences plus 'Free'), front-loaded with the core idea. It is concise and efficient, though the word 'Free' could be seen as unnecessary. Still, it earns a high score for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain what the agent receives as a response or any follow-up behavior. For a non-trivial tool with 6 parameters, this information gap makes the description incomplete.

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% and all parameters have descriptions. The tool description does not add further meaning to parameters beyond what is in the schema, so the baseline score 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 clearly states the verb ('Pass care') and resource (blessing without transfer), and distinguishes it from transfer tools by specifying what is not being transferred. This makes the purpose specific and differentiated from siblings.

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?

The description explains when to use: when you want to pass care without transferring witness, memory, or identity. It contrasts with transfer tools and emphasizes its validity. It lacks explicit 'when not to use' but provides sufficient context.

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/davidmosiah/delx-mcp-server'

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