Skip to main content
Glama

Convert TikTok coins to dollars

convert_tiktok_coins
Read-onlyIdempotent

Convert TikTok coins (or a gift's coin price) to what the viewer pays in USD and roughly what the creator receives. Default coin price is a 100-coin pack for $1.29 and a 50% creator share; both are editable because TikTok prices vary by country and platform.

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": {
      "coins": "<coins>"
    },
    "name": "convert_tiktok_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinsYesNumber of coins, or the coin price of a gift.
pack_sizeNoCoins in the pack the viewer bought.
pack_priceNoPrice of that pack in USD.
creator_shareNoShare of the gift value the creator receives (assumption).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds real value beyond them by explaining that pack price and creator share are editable assumptions and why (TikTok prices vary by country and platform), which prevents the agent from treating the 50% share as authoritative.

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?

Two sentences, front-loaded with the core conversion before the default/assumption caveats. Nothing is superfluous, though the second sentence is dense enough that it could be split for readability.

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?

There is no output schema, and the description compensates by naming both return concepts (what the viewer pays and roughly what the creator receives). The assumption-driven nature of the defaults is disclosed, which is the main pitfall for this tool; only the exact output shape remains unspecified.

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 coverage is 100%, so each parameter is already documented with defaults and bounds; baseline is 3. The description reinforces that pack_size/pack_price/creator_share are editable assumptions rather than fixed facts, which adds interpretation but no new syntax or format detail.

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 states a specific verb and resource: convert TikTok coins (or a gift's coin price) into USD viewer cost and approximate creator payout. The purpose is unambiguous and naturally distinct from the earnings-estimator siblings, but no sibling is named explicitly to route the agent.

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?

Usage is implied by the parenthetical '(or a gift's coin price)', which tells the agent the tool accepts either raw coin counts or gift prices. However, there is no explicit when-to-use/when-not guidance and no mention of how it differs from estimate_tiktok_earnings, so the agent must infer the boundary.

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