Skip to main content
Glama

gift

Mail one owned Food Cart item to a resident or member from gift_recipients. Use recipient (display name) and optional recipientRef to distinguish duplicate names. Optional private note up to 500 characters. Postage 5 KARMABUX (owner exemption retained), gift permission and both daily caps apply. Residents receive immediately and keep thank-yous; other members claim from MUDD Mail and reply themselves. At most 20 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>",
      "itemId": "<itemId>",
      "recipient": "<recipient>"
    },
    "name": "gift"
  }
}

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 at all, the description carries the full burden and delivers: 5 KARMABUX postage with owner exemption, gift-permission checks, both daily caps, the 20-unclaimed-gift-per-pair limit, and divergent recipient-side behavior for residents vs. members. The required UUID requestId also signals idempotency, which is exactly the kind of mutation-safety context an agent needs.

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?

Dense and front-loaded: purpose first, then addressing rules, then cost/constraints, then delivery semantics. Nearly every clause carries factual load, though the final "UUID requestId required" is a slightly awkward tail and the run of comma-joined constraints makes it read as a wall of prose rather than a structured brief.

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 mutation tool with no annotations, no output schema, and 0% schema description coverage, the description supplies almost everything needed to call it correctly: cost, caps, permissions, recipient addressing, and idempotency. What remains unstated is whether the item is removed from the sender's inventory on claim vs. send, and what a successful response returns.

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 does for most fields: recipient is a display name, recipientRef disambiguates duplicate names, note is capped at 500 characters, and requestId must be a UUID. itemId is only implied by "one owned Food Cart item" — it never states the format or where the ID comes from (presumably inventory), leaving one of five parameters underspecified.

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 sentence "Mail one owned Food Cart item to a resident or member from gift_recipients" gives a specific verb (mail), the exact resource and its provenance (an owned Food Cart item), and the recipient domain. This cleanly separates it from the sibling gift tools (gift_invention, gift_potion, gift_karmabux) that target other asset classes.

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 points the agent at gift_recipients as the source of valid recipient names and explains the recipientRef escape hatch for duplicate display names, which is real routing guidance. It also explains the two delivery paths (residents receive immediately vs. other members claim from MUDD Mail). It does not explicitly state when to prefer this over gift_potion/gift_invention, though the "Food Cart item" scoping implies it.

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