Skip to main content
Glama

TG-Market MCP Server

get_developer_balance

Read-onlyIdempotent

Check the authenticated developer's live USD wallet balance (total, locked, and available) on TG-Market. Strictly requires the user's personal X-API-Key in the MCP session headers (rejects anonymous calls).

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_developer_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely useful context beyond them — the API-key authentication requirement, rejection of anonymous calls, and the fact that the balance is 'live' (not cached). It stops short of rate-limit, error-on-invalid-key, or pagination detail, so it is strong but not exhaustive.

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 sentences, front-loaded with the core purpose and then the auth constraint. Every clause carries information — resource, returned fields, platform, and authentication requirement — with no restatement of the tool name or filler.

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

Completeness5/5

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

For a parameterless, read-only lookup with no output schema, the definition covers the essentials: what is read, whose wallet, that the data is live, what fields come back (total/locked/available), and the authentication precondition. Nothing an agent needs in order to decide to call it or to call it successfully is missing.

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?

There are zero input parameters, so there is nothing the description could meaningfully add beyond the schema; baseline 4 applies. The description does correctly avoid implying any arguments are needed.

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 resource: 'Check the authenticated developer's live USD wallet balance (total, locked, and available) on TG-Market', including the scope (own account) and the sub-values returned. An agent knows exactly what this returns; the only missing element is any explicit contrast with siblings, though none of the listed siblings (catalog, prices, orders, endpoints) overlap with balance retrieval.

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?

Gives clear contextual guidance: it acts on the authenticated developer's own wallet and 'Strictly requires the user's personal X-API-Key in the MCP session headers (rejects anonymous calls)', which tells an agent the prerequisite before calling. It does not name alternatives or state when-not to use it, which keeps it out of 5 territory.

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