Skip to main content
Glama

TG-Market MCP Server

get_platform_intelligence

Read-onlyIdempotent

Get comprehensive, verified information about the TG-Market platform, all products (Stars, Premium, TON Top-up, Channel Boosts, Collectible Gift Visuals, Gift Rentals, Sub-Leasing, TON Vault), live cashback status & tiers from /api/cashback-info, commissions/fees, rate limits, and wallet top-up methods.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_platform_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoWhich section of platform intelligence to retrieve (default: 'all').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so safety is covered. The description usefully adds that the data is "verified" and sourced live from /api/cashback-info, but it says nothing about freshness, caching, or response size for the "all" section.

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?

A single front-loaded sentence that packs the resource scope efficiently. The long parenthetical product list is dense but does real work by telling the agent what coverage to expect; it could be trimmed slightly without loss.

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 one-parameter read-only lookup with full schema coverage and no output schema, the description gives adequate scope and content signals. Minor gaps are the absence of output-shape hints and any note about how large the "all" response is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents the single section parameter at 100% coverage with an enum of values, so the baseline is met by structured data alone. The description adds meaning by tying the enum values to concrete content (fees, cashback tiers, top-up methods) and by naming the upstream endpoint for cashback status.

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?

States a specific verb and a broad resource: "Get comprehensive, verified information about the TG-Market platform", then enumerates the covered domains (products, cashback, fees, rate limits, top-up methods). This is clearly distinguishable from siblings like get_live_prices or get_developer_balance, though it never explicitly contrasts itself with them.

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: an agent should call this to learn about the platform, its products, fees, and cashback before acting. There is no explicit when-to-use/when-not statement and no pointer to sibling tools such as get_endpoint_specification for API details, so routing must be inferred.

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