Skip to main content
Glama

Convert Stars

price_in
Read-onlyIdempotent

Use this only to convert a price in Telegram Stars into TON or USD at the display rates GiftChecker uses. Do not use it to look up what a gift costs.

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": {
      "stars": "<stars>",
      "currency": "<currency>"
    },
    "name": "price_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
starsYesAmount in Telegram Stars.
currencyYesTarget currency.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
ratesNo
starsYes
amountYes
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world conversion, so the safety profile is covered. The description adds meaningful context beyond that by pinning the rates to "display rates GiftChecker uses," signalling these are display rates rather than live market rates, though it says nothing about rate freshness or caching.

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

Conciseness5/5

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

Two short sentences with the allowed use front-loaded and the exclusion second. Every clause carries information; nothing is padding.

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?

Output schema exists and annotations cover the safety profile, so the description need only establish purpose and scope for a two-parameter conversion tool, which it does. Only marginal items like rate staleness or rounding conventions are left unstated.

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% and both parameters carry descriptions plus a TON/USD enum, so the schema does the heavy lifting. The description's mention of Stars and the two target currencies only restates what the schema already documents and adds no format or rounding detail.

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?

States a specific verb and resource: converting a Telegram Stars price into TON or USD. It also preempts a confusable purpose by noting it is not for looking up gift costs, so an agent can separate it from gift-lookup siblings without opening a schema.

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?

"Use this only to..." gives an explicit positive condition plus an explicit exclusion ("Do not use it to look up what a gift costs"). It stops short of naming the alternative tool the agent should call for gift prices, leaving that inference to the sibling list.

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