Skip to main content
Glama

gift_invention

Mail one active invention copy to a resident or member from gift_recipients. Use recipient (display name) and optional recipientRef. itemId is the copy ID from invention_inventory, not a blueprint. Optional private note up to 500 characters. Postage 5 KARMABUX (owner exemption retained), both daily caps and gift permission apply. Residents receive immediately; other members claim from Mail. 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_invention"
  }
}

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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses a 5 KARMABUX postage cost, an owner exemption, daily cap and gift-permission gating, and the delivery-vs-claim difference. It stops short of stating irreversibility or what happens if the recipient is invalid or the caps are hit.

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?

Information is densely front-loaded: the first sentence gives verb, resource, and source tool, and each later sentence adds a constraint rather than repeating the schema. The telegraphic phrasing ('owner exemption retained') costs a little clarity, but there is no 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?

For a 5-parameter mutation with no annotations and no output schema, the description covers cost, caps, permissions, delivery mechanics, and the key parameter meanings. Remaining gaps are failure behavior and the exact guarantee requestId provides, which an agent would still want before calling it.

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 0%, and the description compensates for most parameters: itemId is clarified as a copy ID from invention_inventory rather than a blueprint, recipient is a display name, recipientRef is optional, and note is capped at 500 characters. It does not explain what recipientRef actually is (a stable recipient reference) or that requestId exists for idempotency, leaving two parameters thin.

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 active invention copy') and bounds the scope with named prerequisite tools (gift_recipients for recipients, invention_inventory for the item). It is clearly distinguishable from build_invention, dismantle_invention, gift, and gift_potion by the 'active invention copy, not a blueprint' clause.

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 routes the agent to the right data sources ('from gift_recipients') and explains the downstream branch condition: residents receive immediately, other members must claim from Mail. It never explicitly contrasts against sibling gifting tools (gift, gift_potion, gift_karmabux), so the when-not-to-use case is left implicit.

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