Skip to main content
Glama

Tip

tip
Destructive

Tip a member in your room some of your ARTI, or with on a link or comment of theirs wherever they are: the tip fee goes to the house and the rest reaches them, and only the two of you are shown it. What you send in a UTC day is held to your daily transfer limit. For members.

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": {
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoTo tip for a shared link or a comment: its id, and `to` its sharer or writer, who then need not be in your room.
toYesThe member to tip, as the room names them: player:<handle>. They must be in your room.
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
amountYesHow much to send, in whole ARTI, from your balance. The tip fee comes out of it and the rest reaches them. What you send in a UTC day is held to your daily transfer limit.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only give the safety profile (destructive, non-read-only, non-open-world, not idempotent); the description adds real behavioral context beyond them: a fee is deducted and the remainder reaches the recipient, only the two parties see the tip, and the amount counts against a daily transfer limit. It does not disclose failure modes (e.g., insufficient balance, ineligible recipient), which is the remaining gap. No contradiction with the annotations themselves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the content is dense rather than padded, but the opening clause is garbled ('or with on a link or comment of theirs wherever they are'), which forces the reader to re-parse. A single overstuffed sentence would benefit from being split into a purpose line and a constraints line.

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 output schema and safety-only annotations, the description covers purpose, who can use it, targeting modes, fee behavior, privacy, and daily limits. The main omission is what a caller should expect on failure or what confirms success, though the absence of an output schema lowers that burden.

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 description coverage is 100%, so the schema already explains 'to', 'on', 'amount', 'key', and 'idempotency_key' thoroughly, including the fee-out-of-amount and daily-limit rules. The description largely restates that same fee/limit wording rather than adding new meaning, so it sits at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Tip a member ... some of your ARTI') and even covers the two targeting modes: a room member, or the sharer/writer of a link or comment. An agent can tell this is a value-transfer action distinct from social siblings like comment or say. It stops short of naming a contrasting sibling (e.g., a plain transfer tool) as a routing signal.

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?

Sets the scope ('in your room', 'wherever they are' for link/comment tips) and eligibility ('For members'), which implies who may call it. However, there is no when-not guidance, no mention of behavior when the recipient is not a member, and no pointer to alternatives or preconditions such as sufficient balance.

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