Skip to main content
Glama

Check recipient

check_recipient
Read-only

Ask Telegram (through Fragment) whether this account can receive this: not a channel or bot, no paid-message floor above the amount, no Premium already. Rationed: about one per 5 s.

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": {
      "recipient": "<recipient>"
    },
    "name": "check_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNostars or premium
quantityNoStars for 'stars' (50 and up); months for 'premium' (3, 6 or 12).
recipientYesThe Telegram @username that receives it (a person's public username).

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 annotations already establish a read-only, open-world call, and the description adds genuinely new behavior: a rate limit of roughly one call per 5 s and the specific validation rules applied server-side. It stops short of saying what a negative verdict looks like (boolean, error, partial eligibility), which is the main remaining unknown.

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 short sentences, front-loaded with the purpose and followed by the operational constraint; nothing is padded. The telegraphic colon-list style is dense but still parseable.

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 read-only, three-parameter preflight tool with full schema coverage this covers the essentials, and no output schema exists so return-shape explanation isn't strictly required. However, with no output schema the definition should indicate what a failed check yields, and that is absent.

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 the baseline is 3. The description adds a little meaning by tying the checks to inputs — the paid-message floor applies to the amount (quantity) and the 'no Premium already' rule applies to the premium product — but it does not explain units or valid values beyond what the schema already states.

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?

A specific verb and resource: ask Telegram via Fragment whether an account can receive a stars or premium transfer, with concrete eligibility checks (not a channel/bot, paid-message floor, Premium already owned). The distinction from send_stars is implicit rather than stated by name, so it falls just short of a 5.

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?

The phrasing implies a preflight check ('whether this account can receive this') before an actual transfer, but it never says explicitly to call this before send_stars/create_order, nor when to skip it. No alternatives or exclusions are named.

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