Skip to main content
Glama

gift_potion

Mail one owned potion to a resident or member from gift_recipients. Use recipient (display name) and optional recipientRef. itemId accepts an owned potion ID or recipe ID from ingredient_catalog. Optional private note up to 500 characters. Postage 5 KARMABUX (owner exemption retained), both daily caps and gift permission apply. Residents receive immediately and keep thank-yous; other members claim from Mail and reply themselves. UUID requestId required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "requestId": "<requestId>",
      "itemId": "<itemId>",
      "recipient": "<recipient>"
    },
    "name": "gift_potion"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
itemIdYes
recipientYes
requestIdYes
recipientRefNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recipientRef
      Added value: +{
      +  "pattern": "^recipient_[a-f0-9]{64}$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the 5 KARMABUX postage with owner exemption, both daily caps, the gift permission requirement, and the divergent post-send behavior (residents receive immediately and keep thank-yous; other members claim from Mail and reply themselves). It also declares requestId as an idempotency key.

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?

A single dense but front-loaded passage; the action, the recipient source, and the itemId source come first, with cost and delivery semantics after. It is a wall of clauses rather than structured sentences, and "UUID requestId required" is tacked on awkwardly, but no sentence is padding.

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?

For a paid mutation with no output schema and no annotations, the description covers cost, limits, permissions, idempotency, and downstream recipient behavior. It omits what a successful send returns and never mentions cancel_gift as the recovery path, which are the only material gaps for an agent planning this call.

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 description coverage is 0%, so the description must compensate and largely does: itemId is explained as accepting either an owned potion ID or a recipe ID from ingredient_catalog, recipient is clarified as a display name, note carries its 500-character bound, and requestId is called out as required. recipientRef is only labelled "optional" without saying what reference it holds or where to obtain it.

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?

States a specific verb and resource ("Mail one owned potion") plus the eligible recipient pool, which cleanly separates it from the sibling gift tools (gift, gift_invention, gift_karmabux) that share the same verb but different payloads.

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?

Explicitly routes the agent to gift_recipients for valid recipients and to ingredient_catalog for itemId, and states the preconditions (postage, daily caps, gift permission) that gate a successful call. It does not say when to prefer this over the generic gift sibling, which is the one remaining routing gap.

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