Skip to main content
Glama

gift_karmabux

Send a positive whole amount of KARMABUX to someone on gift_recipients. Use recipient (display name) and optional recipientRef to disambiguate. Residents receive it immediately; other members receive a pending MUDD Mail gift to claim. No postage; existing gift permission and both spending caps apply. At most 20 outstanding unclaimed gifts per sender/member pair. 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>",
      "recipient": "<recipient>",
      "amount": "<amount>"
    },
    "name": "gift_karmabux"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
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.4/5.0
Behavior5/5

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

With no annotations at all, the description carries the full behavioral burden and does so well: it discloses the immediate-delivery vs pending-MUDD-Mail-claim split by recipient type, that no postage is charged, that gift permission and both spending caps are enforced, and the hard limit of 20 outstanding unclaimed gifts per sender/member pair. These are exactly the preconditions and side effects an agent needs before a mutation.

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?

Five short sentences, front-loaded with what the tool does, then call mechanics, delivery behavior, constraints, and limits. There is no filler; the telegraphic style is dense with information rather than 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 four-parameter mutation with no annotations and no output schema, the description covers preconditions, delivery outcomes, and rate limits thoroughly. Gaps remain around what a successful call returns (gift identifier, confirmation) and failure modes such as insufficient balance or cap exhaustion, which an agent would need for error handling.

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 it names all four parameters with meaning: recipient as a display name, recipientRef as an optional disambiguator, requestId as a required UUID, and amount as a positive whole number. It stops short of stating idempotency semantics for requestId or how recipientRef is obtained beyond the pattern in the schema, but the roles are clear.

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 opens with a specific verb and resource: 'Send a positive whole amount of KARMABUX to someone.' The currency-specific phrasing separates it from the item-gifting siblings (gift, gift_potion, gift_invention) and it explicitly routes recipient discovery to gift_recipients, so an agent can place it in the tool family immediately.

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 gives operative guidance for the call itself ('Use recipient ... and optional recipientRef to disambiguate') and points at gift_recipients for finding recipients, but never states when to prefer this over cancel_gift or sent_gifts, or when a gift should not be sent. Usage is implied rather than framed as alternatives.

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