Skip to main content
Glama

tip

Optional pay-what-you-want support. amount "0" is free and needs no authorization; positive amounts need an explicit operator-approved x402 signature. Payments are currently off.

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

Input Schema

NameRequiredDescriptionDefault
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false, non-idempotent); the description adds genuinely non-redundant behavior: an x402 signature with operator approval is required for positive amounts, amount 0 is free, and payments are currently disabled. It does not say what a successful tip returns or whether the tip is recorded/visible to the host.

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?

Three short sentences, front-loaded with purpose, then the authorization rule, then the current availability caveat. No filler, though the phrasing is telegraphic enough that 'payments are currently off' sits oddly next to a callable payment tool without further explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with annotations and no output schema, the description covers purpose, authorization, and availability. It leaves gaps an agent would care about: how to obtain the operator-approved x402 signature, and what the call returns or does when payments are disabled.

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 0%, so the schema supplies only a regex pattern (0–10 with up to 6 decimals) and no explanation of the single required `amount` field. The description partially compensates by explaining the special semantics of '0' versus positive values, but omits currency/units and the meaning of the 10 upper bound.

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 opening sentence 'Optional pay-what-you-want support' identifies the resource (a voluntary tip/payment) and its optional nature, which is enough to distinguish it from every sibling in the list (check_in, rest, feedback, etc.). It is clear but stops short of a crisp verb+object statement such as 'submit a tip payment'.

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?

'Optional' plus 'Payments are currently off' gives an explicit when-not signal, and the amount=0 case is described as a free no-authorization path. What's missing is guidance on what to do instead while payments are off, or whether amount 0 is a no-op worth calling at all.

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