Skip to main content
Glama

Arti's

by bar.artis
OverviewDiscussionsAdmin

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.

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?

The description adds meaningful behavior beyond the annotations: the fee goes to the house, the remainder reaches the recipient, only the two parties see it, and daily transfer limits apply. It aligns with destructiveHint=true and does not contradict any annotation.

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?

The purpose is front-loaded, but the main sentence is awkwardly phrased, including the typo-like 'or with on a link', and the trailing 'For members.' is vague. It is not excessively long, but structure and clarity could be tighter.

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 financial mutation tool with no output schema, the description covers the key behavioral context: fee handling, privacy, daily limits, and membership. It does not explain error behavior or response shape, but the schema covers idempotency and parameters.

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 documents all five parameters in detail. The description reinforces the purpose of 'on' and 'amount' but adds little parameter-level meaning beyond the 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?

The description uses a specific verb and resource: tip a member ARTI, optionally on a link or comment. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as act, vote, or share.

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 implies usage by describing tipping a member in your room or on their link/comment, and notes 'For members.' However, it gives no explicit when-to-use versus alternatives or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Arti's toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources